all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Branham <branham@utexas.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 35164@debbugs.gnu.org, Emanuel Berg <moasenwood@zoho.eu>
Subject: bug#35164: 25.1; `re-search-forward' docstring args
Date: Sat, 06 Apr 2019 10:15:09 -0500	[thread overview]
Message-ID: <87lg0n88si.fsf@utexas.edu> (raw)
In-Reply-To: <83imvr9p9v.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 06 Apr 2019 17:33:48 +0300")

On Sat 06 Apr 2019 at 17:33, Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Emanuel Berg <moasenwood@zoho.eu>
>> Cc: 35164@debbugs.gnu.org
>> Date: Sat, 06 Apr 2019 16:30:54 +0200
>> 
>> Eli Zaretskii wrote:
>> 
>> > I don't think I understand how this answers
>> > my question. Please humor me and provide
>> > a direct answer.
>> 
>> I'm dropping this issue 100%. I thought it
>> would be a quick fix, but if you want
>> docstrings that do not conform with your own
>> rules do it.
>
> Which rules, please?  I really don't think I understand that, and I
> don't think I asked something that should trigger such a reaction.  I
> mean, if you submit a bug report, and I ask for clarifying it, why
> would you refuse?

I think this is a duplicate of bug#25193, which was fixed in the
emacs-25 branch but wasn't in Emacs 25.1; it first appeared in Emacs
25.2. See commit 0c55cf43e61537364ee7ea3d6ba77bb6ac3ef8a3.

Alex





  parent reply	other threads:[~2019-04-06 15:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05 18:59 bug#35164: 25.1; `re-search-forward' docstring args Emanuel Berg
2019-04-06  6:17 ` Eli Zaretskii
2019-04-06  7:09   ` Emanuel Berg
2019-04-06  8:59     ` Eli Zaretskii
2019-04-06 14:30       ` Emanuel Berg
2019-04-06 14:33         ` Eli Zaretskii
2019-04-06 14:35           ` Emanuel Berg
2019-04-06 15:15           ` Alex Branham [this message]
2019-04-06 15:57             ` 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=87lg0n88si.fsf@utexas.edu \
    --to=branham@utexas.edu \
    --cc=35164@debbugs.gnu.org \
    --cc=eliz@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.