From: John Williams <jrw@pobox.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 28790@debbugs.gnu.org
Subject: bug#28790: [PATCH] Replaced "which see" with "q.v.".
Date: Sat, 14 Oct 2017 15:52:16 -0700 [thread overview]
Message-ID: <CAEdRJLCPcyuAkispH57vyyfGeV0v9nsEf4hqru8yc=+AK-K17Q@mail.gmail.com> (raw)
In-Reply-To: <c9d15ppent.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
I was trying to make the least disruptive change I could, but if simply
removing the redundant text would be more acceptable, I'd be happy to
rework my patch to do that.
On Oct 14, 2017 3:07 PM, "Glenn Morris" <rgm@gnu.org> wrote:
> Eli Zaretskii wrote:
>
> > The absolute majority of your proposed changes are in the doc strings,
> > where we already have a direct link to the documentation of a symbol
> > whose name precedes "which see". So whether the reader understands
> > that or doesn't, the link is already there to click on, and no harm is
> > done by a relatively rare use of this phrase.
>
> IMO there is no benefit either, as you explain above. "which see" is an
> anachronism in the age of hyperlinks. Is there any logic to where these
> "rare uses" appear - why do some links get them and most not? If there's
> no logic and no benefit, they should be removed as unnecessary verbiage.
>
[-- Attachment #2: Type: text/html, Size: 1272 bytes --]
next prev parent reply other threads:[~2017-10-14 22:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 21:22 bug#28790: [PATCH] Replaced "which see" with "q.v." John Williams
2017-10-12 1:44 ` Nick Helm
2017-10-12 3:51 ` Drew Adams
2017-10-12 6:48 ` Eli Zaretskii
2017-10-14 22:07 ` Glenn Morris
2017-10-14 22:52 ` John Williams [this message]
2017-10-15 2:36 ` Eli Zaretskii
2017-10-15 0:19 ` João Távora
2017-10-15 1:03 ` John Williams
2017-10-15 15:31 ` Drew Adams
2017-10-16 1:55 ` Richard Stallman
2017-10-16 21:47 ` Alan Third
2017-10-15 2:36 ` Eli Zaretskii
2017-10-13 0:26 ` bug#28790: " Richard Stallman
2017-10-13 18:34 ` John Williams
2017-10-13 18:55 ` Eli Zaretskii
2019-06-24 15:39 ` Lars 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='CAEdRJLCPcyuAkispH57vyyfGeV0v9nsEf4hqru8yc=+AK-K17Q@mail.gmail.com' \
--to=jrw@pobox.com \
--cc=28790@debbugs.gnu.org \
--cc=rgm@gnu.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.