all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 15730@debbugs.gnu.org
Subject: bug#15730: 24.3.50; (emacs) `Query Replace' mentions multi-buffer q-r, but no explanation
Date: Mon, 10 Feb 2014 14:19:45 -0800 (PST)	[thread overview]
Message-ID: <4e07b136-05ab-40b1-b5da-3d55fc9bef4a@default> (raw)
In-Reply-To: <87wqh35wyx.fsf@building.gnus.org>

> It says: ...

> I fail to see how that could be misinterpreted.

Try reading the bug report about it.  You might succeed in seeing.
It specifically says how it can be misinterpreted, starting with
its first words:

  "The descriptions of `Y' and `N' can give the impression that
   ordinary `query-replace' (`M-%', `C-M-%') works across multiple
   buffers."

Is it unclear how they can give that impression?  Does reading
their descriptions help?

  `Y (Upper-case)'
   to replace all remaining occurrences in all remaining buffers in
   multi-buffer replacements...

> > Move the link pointing to `Operating on Files' to the paragraph
> > where `Q' is mentioned.  Or add a link there and keep also the
> > one at the page bottom.
>  
> Seems to be fixed.

Not at all.  Read what I wrote.  You just quote the existing doc
that needs to be fixed.  Nothing has been changed at all.

> Closing.

Reopening.  You've done nothing here but close the bug.

I'm sorry to say it, but you don't read the doc (well), and you
don't read the bug reports (well).  You seem to be in a hurry
to close things without bothering to learn about them, let alone 
trying to fix them.

Do you think users write bug reports for fun, or just so you
can close them?  We're trying to improve Emacs, not get an
award for the number of bugs closed without looking.





      reply	other threads:[~2014-02-10 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-27  4:47 bug#15730: 24.3.50; (emacs) `Query Replace' mentions multi-buffer q-r, but no explanation Drew Adams
2014-02-10  5:59 ` Lars Ingebrigtsen
2014-02-10 22:19   ` Drew Adams [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=4e07b136-05ab-40b1-b5da-3d55fc9bef4a@default \
    --to=drew.adams@oracle.com \
    --cc=15730@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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.