all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stefan@marxist.se, 39215@debbugs.gnu.org
Subject: bug#39215: Hyperlinks to man pages in doc strings
Date: Wed, 22 Jan 2020 20:39:53 -0500	[thread overview]
Message-ID: <E1iuRTN-0006ci-Jl@fencepost.gnu.org> (raw)
In-Reply-To: <835zh4wxwt.fsf@gnu.org> (message from Eli Zaretskii on Tue, 21 Jan 2020 18:56:50 +0200)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Why should we cater so much to non-GNU systems?  The users of BSD can
  > install the Info manual as well, can they not?

That is the right approach.  Let's focus our work on improvements that
are beneficial in the GNU system (as well as, possibly, elsewhere).

-- 
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







  parent reply	other threads:[~2020-01-23  1:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21  8:55 bug#39215: Hyperlinks to man pages in doc strings Stefan Kangas
2020-01-21 15:36 ` Eli Zaretskii
2020-01-21 16:32   ` Stefan Kangas
2020-01-21 16:56     ` Eli Zaretskii
2020-01-22  4:03       ` Glenn Morris
2020-01-22 15:45         ` Eli Zaretskii
2020-01-23  1:39       ` Richard Stallman [this message]
2020-01-23  3:14         ` Stefan Kangas
2020-01-24  2:58           ` Richard Stallman
2021-09-25  1:07             ` Stefan Kangas
2021-09-25  1:13               ` Lars Ingebrigtsen
2021-09-25  2:10                 ` Stefan Kangas
2021-09-25  1:32               ` Phil Sainty
2021-09-25  2:10                 ` Stefan Kangas

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=E1iuRTN-0006ci-Jl@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=39215@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stefan@marxist.se \
    /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.