From: Micha Wiedenmann <mw-u1@gmx.de>
Subject: conflict between `gnus-group-universal-argument' and `gnus-group-process-prefix'
Date: 23 Sep 2002 13:41:37 +0200 [thread overview]
Message-ID: <87sn017fyu.fsf@ID-56226.news.dfncis.de> (raw)
Hi,
just a question:
What happens if anybody uses `gnus-group-universal-argument' and
`gnus-group-process-prefix' resp.
`gnus-summary-universal-argument' and `gnus-summary-work-articles'?
I don't see anything to prevent this.
Micha
--
The problem with troubleshooting is that sometimes the trouble shoots back.
next reply other threads:[~2002-09-23 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 11:41 Micha Wiedenmann [this message]
2002-12-29 16:41 ` Lars Magne Ingebrigtsen
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=87sn017fyu.fsf@ID-56226.news.dfncis.de \
--to=mw-u1@gmx.de \
--cc=mw-r1@gmx.de \
/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).