Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: ding@gnus.org
Subject: Re: Add to gnus-visible-headers
Date: Sun, 09 Oct 2022 08:06:43 +0200	[thread overview]
Message-ID: <87tu4djzt8.fsf@dataswamp.org> (raw)
In-Reply-To: <871qrjoain.fsf@tullinup.koldfront.dk>

Adam Sjøgren wrote:

>> (setq gnus-visible-headers "existing\\|new").
>>
>> That works, but is there a simpler way (and shorter) of
>> just appending the new headers?
>
> You could do:
>
>    (setq gnus-visible-headers (concat gnus-visible-headers "\\|new"))

You (the OP) can also use this method which really is cool 

(setq auto-mode-alist `(
    ("\\.bal\\'"     . balance-mode)
    ("\\.cl\\'"      . common-lisp-mode)
    ("\\.dat\\'"     . gnuplot-mode)
    ("\\.gpi\\'"     . gnuplot-mode)
    ("\\.grm\\'"     . sml-mode)
    ("\\.lu\\'"      . lua-mode)
    ("\\.nqp\\'"     . perl-mode)
    ("\\.php\\'"     . html-mode)
    ("\\.pic\\'"     . nroff-mode)
    ("\\.pl\\'"      . prolog-mode)
    ("\\.sed\\'"     . conf-mode)
    ("\\.service\\'" . conf-mode)
    ("\\.tap\\'"     . gcode-mode)
    ("\\.tex\\'"     . latex-mode)
    ("\\.xr\\'"      . conf-xdefaults-mode)
    ("keys\\'"       . conf-mode)
    ("*"             . text-mode)
  ,@auto-mode-alist) )

> but if it's simpler and shorter, I'm not sure. At least you
> aren't hardcoding the existing value :-)

You mean like this? What's wrong with that? :)

(setq gnus-visible-headers '(
                             "^Bcc:"
                             "^Cc:"
                             "^Date:"
                             "^From:"
                             "^Subject:"
                             "^To:"
                             ))

-- 
underground experts united
https://dataswamp.org/~incal



  parent reply	other threads:[~2022-10-09  6:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05  9:14 Colin Baxter
2022-10-07 16:37 ` Adam Sjøgren
2022-10-08  8:49   ` Colin Baxter
2022-10-09  6:06   ` Emanuel Berg [this message]
2022-10-07 16:44 ` Eric S Fraga
2022-10-08  8:48   ` Colin Baxter

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=87tu4djzt8.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --cc=ding@gnus.org \
    /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).