From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>
Cc: 3395@emacsbugs.donarmstrong.com
Subject: bug#3395: 23.0.94; Remove colon after option etc. name
Date: Thu, 28 May 2009 19:11:30 +0200 [thread overview]
Message-ID: <4A1EC5C2.4000309@gmx.at> (raw)
In-Reply-To: <454F42E7EE4E4D469F610AF5A18AE342@us.oracle.com>
> I don't use `variable-at-point'. I do use a command that uses Emacs-Lisp symbol
> syntax, which is the right syntax to use here.
So you request a change of cus-edit.el just because you're not able to
write a command that DTRT here ;-)
>> Commands that do not change the syntax table do get this right. Try,
>> for example, info-lookup on such an item. It should even work for
>> unlispified items.
>
> That's fine, but it is totally unrelated to what I reported and requested.
It is related because it can find things you're not able to find.
> This is not about changing the command. It is simply about removing the useless
> colon. Is that too hard?
It might be.
>> Changing customization code is 100% dangerous.
>
> Don't be ridiculous. You are making, in several separate ways, a mountain out of
> a mole hill.
Hence code like
(unless (string-match ":" format)
(error "Bad format"))
in cus-edit.el is something you understand and can explain.
martin
next prev parent reply other threads:[~2009-05-28 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 23:38 bug#3395: 23.0.94; Remove colon after option etc. name Drew Adams
2009-05-26 23:54 ` Drew Adams
2009-05-28 15:15 ` martin rudalics
2009-05-28 15:34 ` Drew Adams
2009-05-28 15:43 ` martin rudalics
2009-05-28 16:08 ` Drew Adams
2009-05-28 17:11 ` martin rudalics [this message]
2009-05-28 18:24 ` Drew Adams
2009-05-28 20:40 ` martin rudalics
2009-05-28 20:57 ` Drew Adams
2011-07-11 16:23 ` Lars Magne Ingebrigtsen
2011-07-11 16:53 ` Drew Adams
2011-07-11 17:04 ` Lars Magne Ingebrigtsen
2011-07-11 17:19 ` Drew Adams
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=4A1EC5C2.4000309@gmx.at \
--to=rudalics@gmx.at \
--cc=3395@emacsbugs.donarmstrong.com \
--cc=drew.adams@oracle.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.