all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Miles Bader <miles@gnu.org>
Cc: sand@priss.frightenedpiglet.com, emacs-pretest-bug@gnu.org, rms@gnu.org
Subject: Re: 23.0.50; `mode-name' variable docs out of date WRT features
Date: Tue, 01 Jan 2008 23:22:59 -0500	[thread overview]
Message-ID: <jwvsl1g97yz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <871w91vsd7.fsf@catnip.gol.com> (Miles Bader's message of "Wed, 02 Jan 2008 12:06:12 +0900")

>> > But this value doesn't work everywhere.  There are files (bookmark.el
>> > is one) that expect the value to be a string, as the manual says.
>> 
>> > Stefan, could you redo that differently, then ack?
>> 
>> No, it'd be a step backward.

> Er, but the documentation _does_ say: "Pretty name of current buffer's
> major mode (a string)." ... and presumably many coders have relied on
> that description... what should they do?

Adapt?
It's not like we never break backward compatibility in such minor ways,
is it?


        Stefan


PS: I would more cynically say that even if the doc had always said it
could contain any "mode-line-format" thingy, 99% of those same coders
would still not have written code to handle the non-string case.
My experience dealing with Elisp packages is that it's mostly written
by copying bad examples on the web rather than by reading the doc.

  reply	other threads:[~2008-01-02  4:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-30 19:12 23.0.50; `mode-name' variable docs out of date WRT features sand
2007-12-31 14:42 ` Richard Stallman
2008-01-02  2:55   ` Stefan Monnier
2008-01-02  3:06     ` Miles Bader
2008-01-02  4:22       ` Stefan Monnier [this message]
2008-01-03  9:50     ` Richard Stallman
2008-01-10  2:16       ` Glenn Morris

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=jwvsl1g97yz.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=miles@gnu.org \
    --cc=rms@gnu.org \
    --cc=sand@priss.frightenedpiglet.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 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.