From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: couple of feature requests, a question
Date: 08 Apr 1996 19:30:42 +0200 [thread overview]
Message-ID: <w8sivfa4o8t.fsf@hler.ifi.uio.no> (raw)
In-Reply-To: <ri768bafzk1.fsf@rs5.tcs.tulane.edu>
wrobert2@mailhost.tcs.tulane.edu (St. Suika Fenderson Roberts) writes:
> GS> gnus-single-article-buffer's value is t
>
> Why does this default to true?
Because I think it's a good idea not to force gratuitous interface
changes upon people. Having multiple article buffers might annoy some
people.
> >> third, a question: what are the "#'"s for in mail-header.el for?
> >> They break compilation under 19.29, but 19.30 doesn't complain, so
> >> I was wondering.
>
> GS> from the Info file:
>
> I know that. I was just wondering what they are for.
Isn't "#'" just Common Lispese for "'"?
> Lars posted something about the 'raw s being in there to deal with the
> fact that emacs dumps one into cc mode if the folder name ends in .cc .
> unless some other MTA/MUA needs the folder to end in .cc it seems the
> most reasonable fix is `don't end your folder names in .cc' rather
> than breaking compression support.
Or "comp.lang.c". I don't think it's inconceivable that people would
want to call a folder something like that -- and they should be able
to. Which is why those `raw's are needed.
--
"Yes. The journey through the human heart
would have to wait until some other time."
next prev parent reply other threads:[~1996-04-08 17:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-07 23:13 St. Suika Fenderson Roberts
1996-04-08 14:10 ` Greg Stark
1996-04-08 16:30 ` St. Suika Fenderson Roberts
1996-04-08 17:23 ` Per Abrahamsen
1996-04-08 17:25 ` Scott Blachowicz
1996-04-08 17:30 ` Lars Magne Ingebrigtsen [this message]
1996-04-09 3:10 ` St. Suika Fenderson Roberts
1996-04-10 0:05 ` Lars Magne Ingebrigtsen
1996-04-09 3:25 ` Jason L Tibbitts III
1996-04-10 0:07 ` Lars Magne Ingebrigtsen
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=w8sivfa4o8t.fsf@hler.ifi.uio.no \
--to=larsi@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).