Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: gnus-group-customize seems to fail
Date: Wed, 21 Mar 2018 17:19:19 +0100	[thread overview]
Message-ID: <87370tpfjs.fsf@mat.ucm.es> (raw)
In-Reply-To: <87woy57hty.fsf@ucl.ac.uk>

>>> "Eric" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:

   > On Wednesday, 21 Mar 2018 at 10:02, Uwe Brauer wrote:
   >> > On Monday, 19 Mar 2018 at 16:43, Uwe Brauer wrote:
   >> 
   >> > Maybe I misunderstand something here but sc-citation-leader is local to
   >> > the summary buffer so its value will not propagate to a message buffer?
   >> > I.e. not a bug.
   >> 
   >> Well but how can I then pass that variable to the message buffer, but
   >> only groupwise?

   > Maybe look at the message package, not gnus, as message is responsible
   > for composing emails?  For instance, you could put some code in
   > message-header-setup-hook which sets the variables you want depending on
   > the contents of the message header?

I found a workaround with bbdb, so for a particular recipient I set that
variable to nil. So far so good.

But then in the sending hook I need a function which resets the variable
to my standard setting. This is for sure a kludge but I don't know how
to do better.




      reply	other threads:[~2018-03-21 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08  8:47 Uwe Brauer
2018-03-09  0:19 ` Tim Landscheidt
2018-03-19 15:43   ` Uwe Brauer
2018-03-19 17:02     ` Eric S Fraga
2018-03-21  9:02       ` Uwe Brauer
2018-03-21  9:58         ` Eric Abrahamsen
2018-03-21 10:46           ` Uwe Brauer
2018-03-21 10:52             ` Eric Abrahamsen
2018-03-21 17:57             ` Andreas Schwab
2018-03-21 18:31               ` Uwe Brauer
2018-03-21 12:07         ` Eric S Fraga
2018-03-21 16:19           ` Uwe Brauer [this message]

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=87370tpfjs.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --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).