From: Mark Borges <mdb@cdc.noaa.gov>
Cc: ding@ifi.uio.no
Subject: Re: gnus-group-post-news
Date: 28 May 1996 14:43:59 -0600 [thread overview]
Message-ID: <vk91eczfxs.fsf@cdc.noaa.gov> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 28 May 1996 21:40:37 +0200
>> On 28 May 1996 21:40:37 +0200,
>> Lars Magne Ingebrigtsen(lars) wrote:
lars> Greg Thompson <gregt@visix.com> writes:
>> now it's going straight into the message composition buffer with the
>> group under the point being the one in the Newsgroup header. me
>> don't like. how does one get the old behavior back?
lars> You can't. However, the Newsgroups line lets you complete over the
lars> available group names. Just remove the group and type in the new one,
lars> using `TAB' to complete.
...almost.
Evidently, you only get to use TAB once (or never, if you have the bad
luck to have a *Completions* buffer already), then I run into this:
------------------------------
Signalling: (buffer-read-only #<buffer "*Completions*">)
erase-buffer()
message-expand-group()
#<compiled-function (from "message.elc") nil "...(13)" [message-newgroups-header-regexp mail-abbrev-mode-regexp mail-abbrev-in-expansion-header-p message-expand-group tab-to-tab-stop] 1 "Expand group names in Newsgroups and Followup-To headers.\nDo a `tab-to-tab-stop' if not in those headers." nil>()
call-interactively(message-tab)
------------------------------
Unfortunately when I use TAB completion, 99% fo the time I use it more
than once successivley.
This is using XEmacs; does GNU Emacs behave differently?
--
-mb-
next prev parent reply other threads:[~1996-05-28 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-28 14:20 gnus-group-post-news Greg Thompson
1996-05-28 19:40 ` gnus-group-post-news Lars Magne Ingebrigtsen
1996-05-28 20:43 ` Mark Borges [this message]
1996-05-28 22:45 ` gnus-group-post-news Steven L Baur
1996-05-28 22:33 ` gnus-group-post-news Sudish Joseph
1996-05-28 22:55 ` GNU Emacs 19.29 Steven L Baur
1996-05-29 0:47 ` Lars Magne Ingebrigtsen
1996-05-29 9:53 ` Per Abrahamsen
1996-05-29 12:05 ` Steinar Bang
1996-05-29 15:00 ` William Perry
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=vk91eczfxs.fsf@cdc.noaa.gov \
--to=mdb@cdc.noaa.gov \
--cc=ding@ifi.uio.no \
/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).