Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: [gnu.emacs.gnus] Re: Group parameters and gnus-boring-article-headers
Date: 02 Nov 2000 09:54:22 -0500	[thread overview]
Message-ID: <2nbsvys9up.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <vaflmvmji93.fsf@lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> What do you guys (and gals?) think about the following patch by Tony?
> I think it is the right thing to do.

Because Gnus may dynamically bind some variables (maybe local
variables in the summary buffer) then switch to the article buffer,
cloning local variables in the article buffer may cause some problems.
The following example illustrates this kind of problems.  In the
article buffer, it still uses the local value, "Article", instead of
the dynamic one, "Dynamic".

    (let (art-buf sum-buf msg)
      (with-temp-buffer
        (setq art-buf (current-buffer))
        (set (make-local-variable 'info) "Article")
        (with-temp-buffer
          (setq sum-buf (current-buffer))
          (set (make-local-variable 'info) "Summary")
          (let ((info "Dynamic"))
            (set-buffer art-buf)
            (setq msg info))
          (set-buffer sum-buf)
          (setq msg (concat msg "; " info))))
      msg)

As an alternative solution, I've installed a patch which enables users
explicitly specify which summary-buffer-local variables should be
globalized (see `gnus-newsgroup-variables'), so that the values could
be used in the article buffer.

ShengHuo



      reply	other threads:[~2000-11-02 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-18 15:12 Kai Großjohann
2000-11-02 14:54 ` ShengHuo ZHU [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=2nbsvys9up.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /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).