From: Mark Hovey <hovey@math.mit.edu>
Subject: Return vs. Linefeed
Date: 01 Oct 1996 07:10:56 -0400 [thread overview]
Message-ID: <nvuohinvt1b.fsf@schauder.mit.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 01 Oct 1996 05:12:47 +0200
I just upgraded to Red Gnus 5.2.40 from an ancient version of September
Gnus. Since I am a low-end user, the main change I noticed is that it
is much faster now. Thank you for that!
I do have a complaint/question though. In the old version, in the new
newsgroup dialog (You know: Descend hirearchy rec ([y]nsq)?), if I hit
return it would do the default (y in this case). Now it beeps at me
when I hit return, but if I hit linefeed (\C-j) it does the default.
I don't like this behavior. Why was it instituted? I know I could fix
it by a suitable keymap change, but I would have to go hacking through
the gnus lisp files to find the right place.
Lars, are you interested in changing this back? If not, do you know
which lisp file I should look at to figure out how to do it myself?
Mark Hovey
prev parent reply other threads:[~1996-10-01 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-01 3:12 Red Gnus v0.46 is released Lars Magne Ingebrigtsen
1996-10-01 11:10 ` Mark Hovey [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nvuohinvt1b.fsf@schauder.mit.edu \
--to=hovey@math.mit.edu \
/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 NNTP newsgroup(s).