5 ms·
> But the question is, if you already can code, then why bother with creating elisp-code or an vc code-extension? Today there is a good change that you already
by robenkleene 7y ago
> But the question is, if you already can code, then why bother with creating elisp-code or an vc code-extension? Today there is a good change that you already known some useful tooling-language.
I'm not sure what you're saying here? How does another "useful tooling-language" help if your goal is to customize your editor? I guess what you're saying is why don't you write those customizations in another environment like Bash? The easy answer is you want the bells and whistles of the editor, e.g., you want to process your current selection, for example I have a customization to quickly archive the selected piece of text (I often want to remove some text quickly without having to think about whether I might want it again later). I have lots of little customizations like that.
- slightwinder 7y agoI'm referencing the "1 hour-task", which from my understanding usually does not demand to customize the editor itself. I mean what task would even demand customizing the editor, which would not be possible with other environments like bash, python, ruby, powershell? > The easy answer is you want the bells and whistles of the editor, e.g., you want to process your current selection, for example I have a customization to quickly archive the selected piece of text But you don't need elisp for this. Interweaving external tools is possible in any mature editor, including emacs.
- dmortin 7y ago> I'm referencing the "1 hour-task", which from my understanding usually does not demand to customize the editor itself. I your task involves the same kind of editing, for example, then in emacs it's trivial to write a custom function and bind a key to it, making your task much easier.