Emacs - the editor that STILL doesn't have a simple way to duplicate the current line?
Emacs: The Editor for the Next Forty Years [video]
11–20 of 272 posts
Re: Emacs: The Editor for the Next Forty Years [video]
#12There is an amazing project of converting Emacs into the more modern language - Rust (the C parts of it). It is called REmacs[1]. It is sad that the port of Emacs to Guile[2] didn't work out. And for the people who want to convert their C code to Rust, I quite recommend trying c2rust[3] transpiler and refactoring tool.
[1] https://github.com/remacs/remacs
Re: Emacs: The Editor for the Next Forty Years [video]
#13So the slides say... > Concurrency safety isn’t an accident. So far,only Rust has a good story on concurrency thanks to its type system. Is that really true? I've really enjoyed concurrency in D. http://jordi.inversethought.com/blog/advent-of-d/#day18 How much better can it be? And yes, D's concurrency is also based around types.
Based on that description (haven't used D), it seems to cover similar grounds. But Rust's move semantics means that for message passing in particular you can protect against "use after send" issues.
Re: Emacs: The Editor for the Next Forty Years [video]
#14Emacs - the editor that STILL doesn't have a simple way to duplicate the current line?
Re: Emacs: The Editor for the Next Forty Years [video]
#15Emacs - the editor that STILL doesn't have a simple way to duplicate the current line?
C-S-backspace C-y C-y
That's simple by Emacs standards. :-)
If you need it simpler, write and save a keyboard macro.
Re: Emacs: The Editor for the Next Forty Years [video]
#16Re: Emacs: The Editor for the Next Forty Years [video]
#17There is an amazing project of converting Emacs into the more modern language - Rust (the C parts of it). It is called REmacs[1]. It is sad that the port of Emacs to Guile[2] didn't work out. And for the people who want to convert their C code to Rust, I quite recommend trying c2rust[3] transpiler and refactoring tool. [1] https://github.com/remacs/remacs [2] https://www.emacswiki.org/emacs/GuileEmacs [3] https://git…
reading the GuileEmacs thing it sounds like the project was a success? Is there pushback against using this upstream?
Re: Emacs: The Editor for the Next Forty Years [video]
#18I'm on 20 years now, can easily see it going 40 more.
Re: Emacs: The Editor for the Next Forty Years [video]
#19(from the slides) >I learned Emacs in September, 1983 >It is now November, 2019 >...that’s over thirty six years! >An amazingly long time. Hmm, I think I learned Emacs around the same time. Yes, sometimes I think it is weird that I'm still using it. I get a lot of pushback when I say that the developer environment hasn't advanced amazingly in all those years. Devs will point to one or more rather small incremental im…
No, productivity has increased massively, but not due to better editors or IDEs. Those have shown only marginal improvements, if any. (Is any modern environment more productive than a Lisp Machine or Smalltalk?)
But some of the main productivity drivers are distributed version control systems, dependency management libraries, and sites like GitHub for sharing code and libraries.
Being able to automatically generate a project from a template, and pull in any open source library written by anyone on the planet with a single line in a config file, is amazing.
Also, remote hosting and cloud provisioning to quickly deploy any code to be used by anyone in the world with a web browser. Arguably even app stores by eliminating the need to figure out distribution and payments on your own. (The stuff maybe not everyone considers "development", but is key to the overall productivity of any software project.)
Re: Emacs: The Editor for the Next Forty Years [video]
#20Oh Emacs. A graybeard I respect got me to try it about 5 years ago. I used to walk by his machine and think "wow, in a movie about a hacker, this is what their computer screen would look like". I also thought Magit was pretty damn cool because it made interacting with Git extremely intuitive (once you're comfortable with Emacs). In the years since first picking up Emacs, I have probably spent 100 hours or more config…
But I mean, that's not Emacs fault?