Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: must server be loaded to use Gcc ?
Date: Wed, 27 Mar 2002 17:31:05 -0500	[thread overview]
Message-ID: <m33cylzlq8.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vafadstpv38.fsf@lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> prj@po.cwru.edu (Paul Jarc) writes:
>> Fixing the top-level group names in gnus-newsrc-alist would be easy
>> enough programmatically, but there could be other instance of group
>> names - e.g., in group parameters somewhere.
>
> After the previous step this might not be necessary anymore.  Hm.

I doubt Gnus would be intrusive enough to, e.g., dig into each group's
parameters, look for a posting-style, find a "Gcc" entry, and rewrite
it simply because I changed a group's server.  Nor would I want Gnus
to be that intrusive, since it'd almost certainly go wrong sometimes.

> Along with `G e', one could also change the group name.  Is `G E'
> necessary for that or is there another way?

[G E] is the only way I know of.  But is it safe to do that while Gnus
is running?  Even if you exit Gnus immediately afterwards, there could
be exit hooks, etc., that expect an unprefixed group name.


paul


  reply	other threads:[~2002-03-27 22:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87hen3139k.fsf@nomad.consult-meyers.com>
     [not found] ` <m38z8f57mj.fsf@multivac.cwru.edu>
     [not found]   ` <87sn6mph26.fsf@landhaus.consult-meyers.com>
     [not found]     ` <m3it7i2bu5.fsf@multivac.cwru.edu>
     [not found]       ` <vaf663hex2t.fsf@lucy.cs.uni-dortmund.de>
     [not found]         ` <m3eli52692.fsf@multivac.cwru.edu>
2002-03-27 21:19           ` Kai Großjohann
2002-03-27 22:31             ` Paul Jarc [this message]
2002-03-28  0:54           ` Micha Wiedenmann
2002-03-28  0:05             ` Paul Jarc
     [not found]             ` <vaf7knx136p.fsf@lucy.cs.uni-dortmund.de>
     [not found]               ` <87d6xo29yp.fsf@landhaus.consult-meyers.com>
     [not found]                 ` <vafy9gcy3ou.fsf@lucy.cs.uni-dortmund.de>
     [not found]                   ` <m3it7gpne1.fsf@multivac.cwru.edu>
     [not found]                     ` <slrnaa72nl.j2.nospam.look@nomad.consult-meyers.com>
     [not found]                       ` <m3k7rwnvws.fsf@multivac.cwru.edu>
2002-03-29  9:00                         ` A. L. Meyers
     [not found]                           ` <vafu1qzvaq0.fsf@lucy.cs.uni-dortmund.de>
2002-03-29 15:19                             ` A. L. Meyers
     [not found]                       ` <vaf3cyjwpf9.fsf@lucy.cs.uni-dortmund.de>
     [not found]                         ` <87adsrs915.fsf@nomad.consult-meyers.com>
     [not found]                           ` <vafzo0rxfi2.fsf@lucy.cs.uni-dortmund.de>
     [not found]                             ` <87elhvzixw.fsf@landhaus.consult-meyers.com>
2002-04-04 17:09                               ` Paul Jarc
     [not found]                                 ` <k8z1yduof6u.fsf@alcatel.de>
2002-04-05  8:23                                   ` A. L. Meyers

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=m33cylzlq8.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.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).