From: Dave Goel <deego3@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org, deego3@gmail.com, rms@gnu.org,
monnier@iro.umontreal.ca
Subject: Re: Fixing numerous `message' bugs..
Date: Fri, 07 Dec 2007 13:00:50 -0500 [thread overview]
Message-ID: <87hciugzal.fsf@marie.gnufans.net> (raw)
In-Reply-To: <85fxyel8o8.fsf@lola.goethe.zz> (David Kastrup's message of "Fri, 07 Dec 2007 18:24:39 +0100")
>
>> Here's an idea: make up an argument to `message' that says treat the
>> next argument literally. How about t?
>>
>> (message t STRING) is equivalent to (message "%s" STRING)
>> (message t nil) is equivalent to (message nil)
>>
>> So in the cases that are buggy it suffices to add t as the first argument.
The above is the neatest idea so far. It does not involve a new
function, and makes fixing code really easy. And, any author that desires
a literal treatment can simply use (message t string).
> I don't particularly like it. What about (message t nil 7), what is
> that supposed to return? nil too?
Sure, why not? ((Or, it could return an error. ))
> Anyway, there is little point to make this specific to message. So
> if at all, we would special-case format instead. Which means that
> (stringp (format ...)) is no longer guaranteed to be true.
Can you elaborate? Why should a `message' bug cause changes to
something as general as format? And, how will that fix the problem at hand?
Besides, tweaking `format' will further our non-compatibility with
Common Lisp.
next prev parent reply other threads:[~2007-12-07 18:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 0:14 Fixing numerous `message' bugs D. Goel
2007-12-06 10:56 ` David Kastrup
2007-12-06 14:36 ` Dave Goel
2007-12-06 19:26 ` Glenn Morris
2007-12-06 19:34 ` Dave Goel
2007-12-06 20:21 ` Johan Bockgård
2007-12-07 5:28 ` Glenn Morris
2007-12-07 15:52 ` Dave Goel
2007-12-06 15:53 ` Stefan Monnier
2007-12-06 16:01 ` Dave Goel
2007-12-06 16:49 ` Stefan Monnier
2007-12-06 16:58 ` David Kastrup
2007-12-06 17:19 ` David Kastrup
2007-12-07 17:17 ` Richard Stallman
2007-12-07 17:37 ` David Kastrup
2007-12-07 17:17 ` Richard Stallman
2007-12-07 17:18 ` Richard Stallman
2007-12-07 17:24 ` David Kastrup
2007-12-07 18:00 ` Dave Goel [this message]
2007-12-07 18:38 ` Stefan Monnier
2007-12-08 0:56 ` Glenn Morris
2007-12-08 2:21 ` Stefan Monnier
2007-12-08 10:55 ` David Kastrup
2007-12-08 19:15 ` Richard Stallman
2007-12-10 17:41 ` Dave Goel
2007-12-10 18:04 ` Jason Rumney
2007-12-10 19:05 ` Dave Goel
2007-12-10 19:56 ` Andreas Schwab
2007-12-10 20:31 ` Dave Goel
2007-12-10 21:19 ` David Kastrup
2007-12-10 22:44 ` Dave Goel
2007-12-10 23:02 ` David Kastrup
2007-12-08 19:15 ` Richard Stallman
2007-12-07 17:18 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hciugzal.fsf@marie.gnufans.net \
--to=deego3@gmail.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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.