3 ms·
Not sure about the OP but having used Emacs for 4 years and being proficient in Elisp, just the fact that I can spend a small amount of time writing Emacs lisp
by zkry 4y ago
Not sure about the OP but having used Emacs for 4 years and being proficient in Elisp, just the fact that I can spend a small amount of time writing Emacs lisp to automate anything. Like for example spending a few minutes to make any Jira ID text a link to the tickets page, list my GitLab ToDos at the bottom of the screen, or perform complex multi-step data manipulations/visualizations accessable from a single key binding. The more things that enter Emacs, the more things can be automated together.
- 7e 4y agoWouldn't those things be better done at a meta-level with watchers/pipes/scripts, or in a build system?
- zkry 4y agoCould be, I guess it just depends on the context. Emacs shines when it involves interactivity. For example, recently I was exploring a large CSV file with some columns being base64 encoded keys. So when exploring this dataset, it was nice to come up with a command to get the item, base64 decode, perform HTTP request, get the response, and display it in another buffer pretty formatted. Making a command to do this in Emacs Lisp is surprisingly easy (just need a few functions like thing-at-point, base64-decode-string, request, insert, display-buffer, and json-mode). A shell script for this use case may lack the desired interactivity.
- michaelteter 4y agoThis would make a great emacs workflow demo video. Maybe I haven’t been searching for these videos in the last few years, but they don’t seem common. However, I think such examples could help developers increase their productivity while also energizing a new generation of emacs users.
- saeranv 4y agoWhat do you mean when you say "interactivity"? I'm a vim user, so I feel like I'm missing some context about how emacs is used or understood here...
- ajitid 4y agoCan you share this piece of code?