unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Xue Fuqiao <xfq.free@gmail.com>, 13810@debbugs.gnu.org
Subject: bug#13810: 24.3.50; Docstring of `newline' is confusing
Date: Mon, 25 Feb 2013 17:43:55 +0100	[thread overview]
Message-ID: <87d2vos5ro.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <jwv7glwtnrl.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 25 Feb 2013 10:30:50 -0500")

On Mon, 25 Feb 2013 10:30:50 -0500 Stefan Monnier <monnier@iro.umontreal.ca> wrote:

>> The doc string of newline says "Call `auto-fill-function'..."; you can
>> only call a function, not a variable (I suppose you can call a variable
>> something, but not just call it).
>
> Yet, I think that newline doesn't call the `auto-fill-function'
> function, but the function contained in the
> `auto-fill-function' variable.

Still, it doesn't "call the variable" ;-).  Anyway, isn't the potential
for confusion here rather limited, since the function auto-fill-function
is a noop just there for its doc string?

Steve Berman





  reply	other threads:[~2013-02-25 16:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25 10:03 bug#13810: 24.3.50; Docstring of `newline' is confusing Xue Fuqiao
2013-02-25 12:23 ` Stephen Berman
2013-02-25 12:48   ` Xue Fuqiao
2013-02-25 13:05     ` Stephen Berman
2013-02-25 13:27       ` Xue Fuqiao
2013-02-25 15:50         ` Eli Zaretskii
2013-02-25 22:33           ` Xue Fuqiao
2013-02-26  3:46             ` Eli Zaretskii
2020-01-25 15:39               ` Stefan Kangas
2020-01-25 17:20                 ` Eli Zaretskii
2020-01-25 18:05                   ` Stefan Kangas
2020-01-25 18:29                     ` Eli Zaretskii
2013-02-25 15:30       ` Stefan Monnier
2013-02-25 16:43         ` Stephen Berman [this message]
2013-02-25 13:18     ` Stephen Berman
2013-02-25 13:35       ` Xue Fuqiao
2020-09-21 14:35   ` 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

  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=87d2vos5ro.fsf@rosalinde.fritz.box \
    --to=stephen.berman@gmx.net \
    --cc=13810@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=xfq.free@gmail.com \
    /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).