Gnus development mailing list
 help / color / mirror / Atom feed
From: Luc Van Eycken <Luc.VanEycken@esat.kuleuven.ac.be>
Subject: Re: yet more Gnus questions & problems
Date: Mon, 17 Jun 1996 17:26:33 +0200	[thread overview]
Message-ID: <9606171526.AA10369@coulomb> (raw)
In-Reply-To: larsi@ifi.uio.no's message

Lars Magne Ingebrigtsen writes:
 > jbw@cs.bu.edu (Joe Wells) writes:
 > 
 > > 2. Can Gnus be made to work with a compressed mail folder via nnfolder?  I
 > >    have a bunch of old mail archives that I would like to keep compressed
 > >    at all times, but also access via Gnus.
 > 
 > It's a tricky question, believe it or not.  If you have a folder
 > called "things.like.tex", you obviously don't want to open it in LaTeX
 > mode.  On the other hand, if you have a folder called "things.gz", you
 > do want it to be uncompressed, quite likely.  Breakage (on files that
 > happen to end with ".tex", ".c") is much worse than missing features,
 > so Gnus (and its backends) regards all files as simple modeless text
 > files.
 > 
 > There should be a separation in Emacs handling of these issues.  ".gz"
 > handling is something quite different than ".tex" handling, so there
 > shoul be a way to suppress the latter while keeping the first.

Actually there is a difference in `auto-mode-alist'. Quoting from the
documentation:
> Alist of filename patterns vs corresponding major mode functions.
> Each element looks like (REGEXP . FUNCTION) or (REGEXP FUNCTION NON-NIL).
> (NON-NIL stands for anything that is not nil; the value does not matter.)
> Visiting a file whose name matches REGEXP specifies FUNCTION as the
> mode function to use.  FUNCTION will be called, unless it is nil.
> If the element has the form (REGEXP FUNCTION NON-NIL), then after
> calling FUNCTION (if it's not nil), we delete the suffix that matched
> REGEXP and search the list again for another match.

Modes to preprocess the contents (e.g. jka-compr) use the second form
"(REGEXP FUNCTION NON-NIL)" while ordinary modes (e.g. tex) use the first
form "(REGEXP . FUNCTION)", so you could use it to distinguish between
those two types of modes.

Best regards,

Luc


  parent reply	other threads:[~1996-06-17 15:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-14  4:48 Joe Wells
1996-06-14  6:29 ` Andy Eskilsson
1996-06-15  1:16 ` Lars Magne Ingebrigtsen
1996-06-15 22:17   ` Joe Wells
1996-06-16  5:13     ` Lars Magne Ingebrigtsen
1996-06-18 23:21       ` article series (was: yet more Gnus questions & problems) Joe Wells
1996-06-19  1:50         ` Sudish Joseph
1996-06-19  7:26           ` Yair Friedman
1996-06-19 12:25             ` Lars Magne Ingebrigtsen
1996-06-19  6:13         ` Lars Magne Ingebrigtsen
1996-06-19  8:18         ` Per Abrahamsen
1996-06-22 20:04           ` Joe Wells
1996-06-17 15:26   ` Luc Van Eycken [this message]
1996-06-18  4:13     ` yet more Gnus questions & problems Lars Magne Ingebrigtsen
1996-06-18  7:23       ` Andy Eskilsson

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=9606171526.AA10369@coulomb \
    --to=luc.vaneycken@esat.kuleuven.ac.be \
    /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).