unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 41026@debbugs.gnu.org, Richard Stallman <rms@gnu.org>
Subject: bug#41026: Improve documentation of `makunbound' and `fmakunbound'
Date: Mon, 04 May 2020 14:52:37 +0200	[thread overview]
Message-ID: <87h7wvyi96.fsf@stefankangas.se> (raw)
In-Reply-To: <87y2q840mt.fsf@igel.home> (Andreas Schwab's message of "Mon, 04 May 2020 09:31:22 +0200")

Andreas Schwab <schwab@linux-m68k.org> writes:

> On Mai 03 2020, Richard Stallman wrote:
>
>> So that those people who may want to use them, even if they are few,
>> can be sure of how to use them.
>
> They are even documented in the manual.  What makes them so special?

They are occasionally useful.  I'm not sure that makes them special.

But again, I'm not sure what you are saying.  Are you proposing to
remove them from the ELisp manual?

Best regards,
Stefan Kangas





  reply	other threads:[~2020-05-04 12:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 13:53 bug#41026: Improve documentation of `makunbound' and `fmakunbound' Stefan Kangas
2020-05-02 14:03 ` Eli Zaretskii
2020-05-02 14:17   ` Stefan Kangas
2020-05-02 14:22     ` Eli Zaretskii
2020-05-02 20:25       ` Stefan Kangas
2020-05-02 21:12         ` Andreas Schwab
2020-05-02 21:30           ` Stefan Kangas
2020-05-04  3:06           ` Richard Stallman
2020-05-04  7:31             ` Andreas Schwab
2020-05-04 12:52               ` Stefan Kangas [this message]
2020-05-04 13:05                 ` Andreas Schwab
2020-05-03 14:21         ` Eli Zaretskii
2020-05-03 20:07           ` Stefan Kangas
2020-05-02 14:55 ` Andreas Schwab
2020-05-02 15:00   ` Stefan Kangas
2020-05-02 15:41     ` Eli Zaretskii
2020-05-02 20:22   ` Drew Adams
2020-05-03  3:43   ` Richard Stallman

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=87h7wvyi96.fsf@stefankangas.se \
    --to=stefan@marxist.se \
    --cc=41026@debbugs.gnu.org \
    --cc=rms@gnu.org \
    --cc=schwab@linux-m68k.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 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).