From: Robert Pluim <rpluim@gmail.com>
To: 35163@debbugs.gnu.org
Cc: Emanuel Berg <moasenwood@zoho.eu>
Subject: bug#35163: 25.1; `narrow-to-region' docstring no mention of args
Date: Thu, 11 Apr 2019 11:46:53 +0200 [thread overview]
Message-ID: <m24l747u2a.fsf@gmail.com> (raw)
In-Reply-To: <86h8b7s5tq.fsf@zoho.eu> (Emanuel Berg's message of "Tue, 09 Apr 2019 14:48:01 +0200")
>>>>> On Tue, 09 Apr 2019 14:48:01 +0200, Emanuel Berg <moasenwood@zoho.eu> said:
Emanuel> Robert Pluim wrote:
>> Using 'Mail-Copies-To: never' is fine
Emanuel> I know, but -
>> as long as you then read the mailing list or the gmane group
>> for your bugs. (I didnʼt CC you on this reply)
Emanuel> - except it isn't in this particular case as the followup
Emanuel> header isn't set correctly IIUC?
Correct.
Emanuel> Perhaps you or someone else can try using
Emanuel> gmane.emacs.bugs as well so we'll see if this is a local
Emanuel> config issue on my part? (Unless we have the same config
Emanuel> that is :))
I use gmane.emacs.bugs all the time, and donʼt have this problem.
Emanuel> The one big problem with Gnus and configs is you can't
Emanuel> really do 'emacs -q' to find out if the problem is with
Emanuel> you or not, a method that _almost_ always is waterproof
Emanuel> in all the other parts of the Emacs World where I'm a
Emanuel> regular.
Yes, thatʼs true. In this case, Iʼd use 'G p', ie
('gnus-topic-edit-parameters') to see if you have any specific
settings for gmane.emacs.bugs. If that doesnʼt turn up anything, then
your .gnus.el and/or .emacs is the next place to look (probably in
posting styles). As a last resort, look in .newsrc.eld
Robert
next prev parent reply other threads:[~2019-04-11 9:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 18:51 bug#35163: 25.1; `narrow-to-region' docstring no mention of args Emanuel Berg
2019-04-05 19:08 ` Eli Zaretskii
2019-04-05 19:26 ` Emanuel Berg
2019-04-06 6:25 ` Eli Zaretskii
2019-04-06 7:10 ` Emanuel Berg
2019-04-06 9:01 ` Eli Zaretskii
2019-04-06 14:32 ` Emanuel Berg
2019-04-08 16:24 ` Glenn Morris
2019-04-08 16:55 ` Eli Zaretskii
2019-04-08 21:14 ` Emanuel Berg
2019-04-08 22:19 ` Basil L. Contovounesios
2019-04-09 0:45 ` Emanuel Berg
2019-04-09 1:09 ` Emanuel Berg
2019-04-09 1:13 ` Basil L. Contovounesios
2019-04-09 8:53 ` Emanuel Berg
2019-04-09 9:37 ` Robert Pluim
2019-04-09 9:55 ` Emanuel Berg
2019-04-09 11:42 ` Robert Pluim
2019-04-09 12:48 ` Emanuel Berg
2019-04-11 9:46 ` Robert Pluim [this message]
2019-04-12 5:27 ` Emanuel Berg
2019-04-09 6:54 ` Eli Zaretskii
[not found] ` <handler.35163.D35163.155474252232285.notifdone@debbugs.gnu.org>
2019-04-08 23:09 ` Noam Postavsky
2019-04-09 0:48 ` Emanuel Berg
2019-04-09 7:08 ` Eli Zaretskii
2019-04-09 6:56 ` Eli Zaretskii
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=m24l747u2a.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=35163@debbugs.gnu.org \
--cc=moasenwood@zoho.eu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.