Marcin Borkowski: Recent Changes

Updates since 2018-10-11 05:00 UTC up to 2018-11-10 05:00 UTC

2018-11-03

08:54 UTC (new) 2018-11-03 A few remarks about defining minor modes . . . . Marcin Borkowski – Today’s post is extremely technical and niche, but I just wanted to share an interesting story I had a few days ago.

2018-10-27

14:46 UTC (new) 2018-10-27 Launching terminal in current directory . . . . Marcin Borkowski – I am a bit ashamed that I do not always use Eshell – I sometimes rely on a “proper” bash in a terminal. (One possible reason is when I ant to run something that does not play too well with Eshell, like top or watch. I know it is possible to do that in Eshell, using eshell-visual-commands, but it seems I’m too lazy (or still too much accustomed to my usual terminal) to change that. Anyway, it is feasible to want to run a terminal (or any other program) in the current directory from Emacs. It turns out that it is easy to do using async-shell-command.

2018-10-22

11:48 UTC (new) 2018-10-22 Running visual commands in Eshell . . . . Marcin Borkowski – It is a known thing that running commands that control the terminal like top in Eshell is problematic – Eshell plays well with commands that take stdin in and put stdout out, but any control codes are just displayed verbatim. Happily, there is a way around it.

2018-10-15

01:51 UTC (diff) Comments on 2018-10-14 Magit and C-u i . . . . Anonymous – s/One grip/One gripe/ Please fix and then delete this comment :)

2018-10-14

23:34 UTC (new) Comments on 2018-10-14 Magit and C-u i . . . . Anonymous – Perhaps you could add such a mention to the manual? https://github.com/magit/magit/blob/master/.github/CONTRIBUTING.md#documentation-contributions . . .
17:59 UTC (new) 2018-10-14 Magit and C-u i . . . . Marcin Borkowski – Last time I mentioned that I use multiple backup copies of my .env file. One problem with that approach was they they cluttered my Git status (or the magit-status window). I could put the relevant pattern in my .gitignore file, but I didn’t want to bother other programmers in the team with peculiarities of my personal setup.