대문 최근에 바뀐 글 새소식 찾기 하우투 문제 제안

TomTromey

I’ve been an Emacs user since 1991 or so, when Brian Fox (of bash fame) caught me using vi and csh, and told me that I ought to switch to Emacs and bash. I’ve never looked back.

I’ve used various versions of Emacs over the years: Emacs 18 was my first, then I used Epoch, Lucid Emacs, XEmacs. These days, I use Emacs.

I wrote a few random hacks that made their way into Emacs. I (re-)wrote Tcl mode, and I added regular expression support to etags.

I’m back to hacking on Emacs after a long hiatus. Recently I’ve been working on notification area support and a packaging system.

My blog is at http://tromey.com/blog/. There’s an RSS feed for just Emacs-related things if that is all you are interested in hearing about.

My Emacs Wish List

Here’s my Emacs wish-list. Parts of it are more like my personal to-do list.

Something like that has been tried. http://www.mundell.ukfsn.org/native/

    • Cool! Of course without profiling I don’t know if it helps. And I think lexical scope is part of the solution… what ever happened to that branch? Will it ever be merged?
    • Could cache function lookup if flet is rarely used. (This doesn’t show up in profiles, so I doubt it is worthwhile.)
    • Looked into an incremental GC. AREF and ASET macros, among others, are inconsistently used; for a write barrier not involving the MMU this would have to be fixed.
      • I did write a huge patch to regularize most of these uses, and to add setter macros for all other lisp object fields. The result is quite ugly, and the patch, while enormous, is still incomplete – there are places in Emacs that take the address of a field and pass it around, which is a no-no for a software write barrier. It isn’t clear that finishing this is worthwhile.
    • Could precompile regexps and have regexp objects available to elisp. (In my one profile run, regexp matching was item #13, and regexp compilation was not visible. But, due to regexp caching, this might not have been the best test.) A nice advantage of first-class regexp objects is that you can support multiple different regexp syntaxes.
  • “q” in view-mode often iconifies the frame. I never want this, in fact I always want “q” to just be bury-buffer. Can view-mode do this, or do I need to make a key binding? (I sent a bug report. RMS replied saying that no-one is expert in view-mode’s quit code right now. That stuff is wacky…)
I couldn’t agree more that the view-mode quit code is a mess. This started with Emacs22, AFAICT. In my case, I never want the frame iconified, and I usually don’t want the buffer buried either: I want the buffer killed (which in my case will also delete the window or frame as appropriate) or I want just ‘quit-window’. The current view-mode quit code is a jungle of possibilities, none of which seem to work well for me. It was simple before. Helas, on n’arrete pas le progres…
I asked for a user option to configure this (although it would be better for view-mode not to try to be so sophisticated, in the first place), but that was rejected. I at least set ‘view-remove-frame-by-deleting’ to ‘t’, but that doesn’t help with the new problems introduced in Emacs22. I also complained about the plethora of similar names for commands to leave view-mode: ‘View-exit’, ‘View-quit’, ‘View-quit-all’, ‘View-leave’, ‘View-kill-and-leave’. That alone should be a signal that there is a design problem. Look at ‘RETURN-TO’ in the doc string of ‘view-mode-exit’ if you want to see how crazy this stuff is. – DrewAdams

CategoryHomepage