From: Bastien <bzg@altern.org>
To: glyn.millington@gmail.com
Cc: help-gnu-emacs@gnu.org, James Freer <jessejazza3.uk@gmail.com>
Subject: XEmacs feature missing in GNU Emacs? (was: XEmacs)
Date: Mon, 29 Apr 2013 18:21:48 +0200 [thread overview]
Message-ID: <8761z51f4z.fsf_-_@bzg.ath.cx> (raw)
In-Reply-To: <871u9t7te9.fsf@nowhere.org> (glyn millington's message of "Mon, 29 Apr 2013 07:17:18 +0100")
glyn.millington@gmail.com writes:
> I suspect that one reason for sticking with Xemacs now is lots of little
> customizations and tweaks which don't easily transfer to Gnu Emacs - the
> same reason why I wouldn't willingly swap my init.el for yours, because
> it would change the way I work.
I changed the subject -- maybe this thread is an opportunity to get a
list of XEmacs features that would be nice to have in GNU Emacs. I'm
not thinking of architectural differences, rather of small convenient
commands or options.
--
Bastien
next prev parent reply other threads:[~2013-04-29 16:21 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 19:25 XEmacs Steven Degutis
2013-04-28 19:28 ` XEmacs James Freer
2013-04-28 21:15 ` XEmacs Glyn Millington
2013-04-28 22:28 ` XEmacs James Freer
2013-04-29 6:17 ` XEmacs glyn.millington
2013-04-29 16:21 ` Bastien [this message]
2013-04-29 17:01 ` XEmacs feature missing in GNU Emacs? Christopher Schmidt
2013-04-29 17:22 ` Steven Degutis
2013-05-01 10:04 ` Christopher Schmidt
2013-04-29 17:04 ` XEmacs feature missing in GNU Emacs? (was: XEmacs) Ian van der Neut
2013-04-29 17:11 ` Ian van der Neut
2013-04-29 17:18 ` Ian van der Neut
2013-04-29 17:38 ` XEmacs feature missing in GNU Emacs? Bastien
2013-04-29 18:47 ` Ian van der Neut
2013-04-30 8:51 ` Bastien
[not found] ` <mailman.24842.1367254876.855.help-gnu-emacs@gnu.org>
2013-04-30 9:19 ` Alan Mackenzie
[not found] ` <mailman.24838.1367252519.855.help-gnu-emacs@gnu.org>
2013-04-29 20:55 ` Dan Espen
2013-04-30 8:55 ` Bastien
2013-04-30 18:48 ` Glenn Morris
[not found] ` <mailman.24911.1367347700.855.help-gnu-emacs@gnu.org>
2013-04-30 19:35 ` Dan Espen
2013-05-01 13:32 ` rusi
2013-04-30 13:48 ` Tassilo Horn
[not found] ` <mailman.24891.1367329755.855.help-gnu-emacs@gnu.org>
2013-04-30 16:18 ` Dan Espen
2013-04-30 18:23 ` Drew Adams
[not found] ` <mailman.24910.1367346251.855.help-gnu-emacs@gnu.org>
2013-04-30 18:35 ` Dan Espen
2013-04-30 19:57 ` Drew Adams
2013-05-04 23:38 ` Stefan Monnier
2013-05-05 1:58 ` J. David Boyd
2013-05-05 2:49 ` Drew Adams
[not found] ` <mailman.25131.1367710708.855.help-gnu-emacs@gnu.org>
2013-05-05 0:34 ` Dan Espen
2013-04-30 20:02 ` XEmacs "Jérôme M. Berger"
2013-05-14 7:20 ` XEmacs Luca Ferrari
[not found] ` <mailman.24804.1367188121.855.help-gnu-emacs@gnu.org>
[not found] ` <kmiima$te5$1@speranza.aioe.org>
2013-05-11 19:08 ` XEmacs unfrostedpoptart
[not found] ` <kmohnv$9nn$1@speranza.aioe.org>
2013-05-12 21:29 ` XEmacs Emanuel Berg
2013-05-13 20:13 ` XEmacs Hils
2013-05-13 21:04 ` XEmacs Emanuel Berg
2013-05-13 22:06 ` XEmacs Glyn Millington
2013-05-17 1:38 ` XEmacs Emanuel Berg
2013-05-15 15:26 ` XEmacs Cecil Westerhof
-- strict thread matches above, loose matches on Subject: below --
2013-04-30 14:01 XEmacs feature missing in GNU Emacs? (was: XEmacs) Buchs, Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761z51f4z.fsf_-_@bzg.ath.cx \
--to=bzg@altern.org \
--cc=glyn.millington@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=jessejazza3.uk@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).