Bad NEWS, Emacs
eshelyaron.com
Bad NEWS, Emacs
1–10 of 250 posts
Re: Bad NEWS, Emacs
#2[flagged]
Re: Bad NEWS, Emacs
#3OpenSource working as intended, no?
Re: Bad NEWS, Emacs
#4[flagged]
Re: Bad NEWS, Emacs
#5[flagged]
[flagged]
Re: Bad NEWS, Emacs
#6Assuming any particular commit in git represents the eventual state of a release seems foolhardy.
Re: Bad NEWS, Emacs
#7I have been using emacs since probably 94. This change, without a toggle from userspace to disable it is a kick in the pants. I will follow your fork until (if) they come around.
Re: Bad NEWS, Emacs
#8OpenSource working as intended, no?
Yup. Great isn't it when the system works as intended.
Re: Bad NEWS, Emacs
#9Assuming any particular commit in git represents the eventual state of a release seems foolhardy.
That's not the author's point. They did try to improve the behavior in a future commit and were shot down. Hard it seems. So were any requests from others to change this before release.
Re: Bad NEWS, Emacs
#10I someone is to fork Emacs its because of getting proper UI integration or multithreading.
This is just a neglectable, whimsical step. Sorry.
What Emacs needs is the nvim/vim Schisma.