Assigning your copyright to the Free Software Foundation helps us defend the GPL and keep software free. Thanks to Nicholas Harrison and Omar Polo Del Vecchio #Emacs for assigning their copyright to the FSF! #GNU
Assigning your copyright to the Free Software Foundation helps us defend the GPL and keep software free. Thanks to Wenshan Ren and Malgi Reddy Rajashekar Reddy #Emacs for assigning their copyright to the FSF! #GNU
Assigning your copyright to the Free Software Foundation helps us defend the GPL and keep software free. Thanks to James Norman Vladimir Cash, Laurence Warne, and Leon Vack #Emacs for assigning their copyright to the FSF! #GNU
Assigning your copyright to the Free Software Foundation helps us defend the GPL and keep software free. Thanks to Alexander Miller, Augusto Ritter Stoffel, and Elo Laszlo #Emacs for assigning their copyright to the FSF! #GNU
Assigning your copyright to the Free Software Foundation helps us defend the GPL and keep software free. Thanks to Fabrice Bauzac-Stehly, Gabriel do Nascimento Ribeiro, and Hao WANG #Emacs for assigning their copyright to the FSF! #GNU
Assigning your copyright to the Free Software Foundation helps us defend the GPL and keep software free. Thanks to YUE Daian #Emacs for assigning their copyright to the FSF! #GNU
@geniusmusing I used to try to learn #emacs every Summer. I finally gave up. It is too complicated (and using non-standard terminology like C-c C-x instead of CTRL-C CTRL-X does not make it any easier) ... I also used to just close my terminal instead of trying to close Emacs.
I thought maybe #Xemacs solved that, but it did not seem to be better.
I don’t think the issue is emacs’ appearance. If they try to develop a beauteous front-end for it, they should make that front-end replace the obscure (and obfuscating) control syntax with something that mere mortals can use. That way, they can deceive themselves into believing that improving the appearance solved their popularity issue.
(Is emacs not popular? I still see blog posts and tutorials where emacs is assumed, though nano is by far the most popular text editor.)
Assigning your copyright to the Free Software Foundation helps us defend the GPL and keep software free. Thanks to Condition-ALPHA Digital Broadcast Technology Consulting, Jaehwang Jung, and SunegKi Kim #emacs for assigning their copyright to the FSF! #GNU
@musicman Yes, I think #git is overly complicated for most projects' needs, but it has mindshare, so people often demand it when another VCS would be more appropriate. It'd be great if transitioning from one to another was a well-understood problem, but it isn't.
Is that #Emacs that is trying to move from #svn to git with #ESR's help and having a difficult time of it?
Assigning your copyright to the Free Software Foundation helps us defend the GPL and keep software free. Thanks to Pieter van Oostrum, tsuucat #emacs and Vyacheslav Petrishchev #Wget for assigning their copyright to the FSF! #GNU
Assigning your copyright to the Free Software Foundation helps us defend the GPL and keep software free. Thanks to Justin Timmons and Klaus Weiss #Emacs for assigning their copyright to the FSF! #GNU
Assigning your copyright to the Free Software Foundation helps us defend the GPL and keep software free. Thanks to Barry Duggan #GNURadio, László Várady #GNUBison, and Tom Gillespie #Emacs for assigning their copyright to the FSF! #GNU
So I have been having a lot of fun using Spacemacs (Emacs + Vim) lately as my new IDE. Its a game changer for sure. One thing I find particularly fun is the "pretty-mode" extensions I managed to program into it (had to write my own layer that I derived from some existing code). I'll explain each aspect of pretty-mode in a second but first check out some screen shots at the bottom of this post to see what it looks like.
Pretty-git is the most functionally useful of them all. When you make a git commit it helps you format your git message using the standard format where you start with one keyword classifying the commit (such as fix, feature, refactor, etc) then a colon, then the text. It provides a list of selectable keywords and adds it to the git message. Moreover it can replace these keywords visually with descriptive icons (such as a little red bug for bug fixes). Later when you look through the git history you see these icons where the keywords should be making for a very nice visual representation.
My favorite is the pretty-code. Its a simple idea, it replaces certain keywords of phrases in code with equivelant mathematical symbols. So, for example null/nil/none will be replaced with the empty-set math symbol (a circle with a slash through it), similarlity stuff like not equals (!=) will be replace with an equals mark with a slash through it. You can fully customize what symbols are replaced and what it is replaced with. Also when you cursor over a symbol it temporarily reverts back to the keyword it replaced so you can see what it means. Searches and of course the underlying code itself (and in git) is unchanged.
pretty-shell is just a shell with some nice font-awesome fonts to make it pretty, usually informative so different icons might represent if a directory is a git repository or if it has staged changes and what not.
Finally pretty-outline. This basically just gives bullet points (useful in org-mode and note dating) some pretty icon representations rather than circles. Pure eye candy on this one.
So I have been having a lot of fun using Spacemacs (Emacs + Vim) lately as my new IDE. Its a game changer for sure. One thing I find particularly fun is the "pretty-mode" extensions I managed to program into it (had to write my own layer that I derived from some existing code). I'll explain each aspect of pretty-mode in a second but first check out some screen shots at the bottom of this post to see what it looks like.
Pretty-git is the most functionally useful of them all. When you make a git commit it helps you format your git message using the standard format where you start with one keyword classifying the commit (such as fix, feature, refactor, etc) then a colon, then the text. It provides a list of selectable keywords and adds it to the git message. Moreover it can replace these keywords visually with descriptive icons (such as a little red bug for bug fixes). Later when you look through the git history you see these icons where the keywords should be making for a very nice visual representation.
My favorite is the pretty-code. Its a simple idea, it replaces certain keywords of phrases in code with equivelant mathematical symbols. So, for example null/nil/none will be replaced with the empty-set math symbol (a circle with a slash through it), similarlity stuff like not equals (!=) will be replace with an equals mark with a slash through it. You can fully customize what symbols are replaced and what it is replaced with. Also when you cursor over a symbol it temporarily reverts back to the keyword it replaced so you can see what it means. Searches and of course the underlying code itself (and in git) is unchanged.
pretty-shell is just a shell with some nice font-awesome fonts to make it pretty, usually informative so different icons might represent if a directory is a git repository or if it has staged changes and what not.
Finally pretty-outline. This basically just gives bullet points (useful in org-mode and note dating) some pretty icon representations rather than circles. Pure eye candy on this one.