unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 34588@debbugs.gnu.org
Subject: bug#34588: 27.0.50; Doc of write-contents-functions: arguments?
Date: Thu, 21 Feb 2019 21:06:08 -0500	[thread overview]
Message-ID: <E1gx0E4-0000QR-Ba@fencepost.gnu.org> (raw)
In-Reply-To: <87imxdxze6.fsf@web.de> (message from Michael Heerdegen on Thu, 21 Feb 2019 10:29:53 +0100)

[[[ 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. ]]]

  > > so the naming convention is preserved and everything should have been
  > > clear.  I believe that due to how the documentation is written,
  > > readers intuitively pay less attention to the "or their return values
  > > are used in some way" and "or their return values are used" phrases.

  > Hmm, you're right, the explanation clearly tells it.  Dunno how to
  > improve it to let people pay more attention - more jokes maybe?

If people work on this, I think they will find a way.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







  reply	other threads:[~2019-02-22  2:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20  3:55 bug#34588: 27.0.50; Doc of write-contents-functions: arguments? Michael Heerdegen
2019-02-20 17:13 ` Eli Zaretskii
2019-02-21  2:59   ` Michael Heerdegen
2019-02-21  3:32   ` Richard Stallman
2019-02-21  3:47     ` Eli Zaretskii
2019-02-21  4:24       ` Michael Heerdegen
2019-02-21  9:17         ` martin rudalics
2019-02-21  9:29           ` Michael Heerdegen
2019-02-22  2:06             ` Richard Stallman [this message]
2021-10-23 18:11               ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1gx0E4-0000QR-Ba@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=34588@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).