Recent Changes

2025-06-07

• 17:12 UTC (new) (history) 2025-06-07 Promisified setTimeout . . . . mbork – For quite a few years, when I needed my Node.js scripts to wait for some time, I used this promisified version of setTimeout:

2025-06-01

• 05:50 UTC (diff) (history) 2025-05-31 Emacs timestamps and Unix time . . . . mbork – Deleted 2025-05-31_Emacs_timestamps_and_Unix_time

2025-05-31

• 18:40 UTC (new) (history) 2025-05-31 Converting integers to ISO-8601 timestamps . . . . mbork – Two weeks ago I wrote about using defcustom​’s :get and :set keywords, allowing the user to set an option containing a Unix timestamp (that is, a number) using an ISO-8601 timestamp. Today I am going to use such an option.

2025-05-26

• 16:02 UTC (new) (history) 2025-05-26 Adding directories to EMMS playlist from Dired . . . . mbork – Like many of us Emacsers, I do much (if not most) my computering in Emacs. This includes using EMMS as my main media player and Dired as my file manager. One thing I find myself doing pretty often is adding a bunch of subdirectories in my ~/music directory to my EMMS playlist. I usually used emms-add-directory-tree, but it is not really smooth if I want to apply it to many subdirectories. I thought, “there must be a function which adds the current item – or the marked items – to the playlist”.

2025-05-19

• 17:38 UTC (new) (history) 2025-05-19 Customization variables which require some computation after being set . . . . mbork – Today I’d like to learn – and then show – how to define a user option in Emacs so that setting it will trigger evaluating some Elisp code. Here is my use-case. I want the option to be a timestamp. The most convenient way to store it is as Unix time (number of seconds since the epoch), since the code using it will perform comparisons between that timestamp and other times. On the other hand, the most convenient way to set it is as ISO-8601 timestamp, which is inifinitely more human-readable than the Unix time.

2025-05-12

• 11:43 UTC (new) (history) Comments on 2025-05-12 Coloring Git output in Magit . . . . Anonymous – > I suppose that the reason it is not advertised may have something to do with performance issues. See also . . .
• 06:23 UTC (new) (history) 2025-05-12 Coloring Git output in Magit . . . . mbork – Today I have a very short and rather niche tip, but maybe someone will find it useful (as I did). Like many other people, I use Magit on a daily basis. One thing that bothered me a bit was the fact that when I pressed $ to see the output of the Git process, all colors were gone. This was a problem for me, since the pre-commit hook I use calls the TypeScript compiler to tell me about any potential problems with types in my code. By default, the output of tsc is colored with the ANSI color codes. While the coloring can be turned out, the setting to do that is rather crude (it also disables pretty-printing/formatting), and after all, these colors serve a purpose and are genuinely useful. I decided that before I turn the formatting off, it may be a good idea to check if Magit has an option to allow coloring the Git output using ANSI codes.

More...