unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'martin rudalics'" <rudalics@gmx.at>
Cc: 3395@emacsbugs.donarmstrong.com
Subject: bug#3395: 23.0.94; Remove colon after option etc. name
Date: Thu, 28 May 2009 13:57:13 -0700	[thread overview]
Message-ID: <B136BABA673B4A6DBF92B64E02E20CAA@us.oracle.com> (raw)
In-Reply-To: <4A1EF6C8.9020601@gmx.at>

>  >>  > This is not about changing the command. It is simply about
>  >>  > removing the useless colon. Is that too hard?
>  >>
>  >> It might be.
>  >
>  > Then I guess you'll have to mark it too hard to fix, and move on.
> 
> You have to find someone who agrees that this is a bug.

I don't have to do any such thing.

This is an enhancement request. Like all bug reports and enhancement requests,
Emacs developers are free to choose not to fix it. I make a request or report a
problem. You decide whether to fix it.

>  >> Hence code like
>  >> 	     (unless (string-match ":" format)
>  >> 	       (error "Bad format"))
>  >>
>  >> in cus-edit.el is something you understand and can explain.
>  >
>  > I don't understand the question or comment.
> 
> Obviously because you didn't try to.

Nothing obvious about it. I do not understand what you are trying to say. You
state that I understand and can explain something, but I have no idea what that
means. What is it that you think I understand and can explain? And why?

>  > What's the point?
> 
> That colons sometimes serve additional purposes in custom buffers
> besides of being displayed as visible characters.

Ah, I see.

I cannot speak to the difficulty of implementing the enhancement. I reported
this from a user point of view, not that of an implementor.

I would _guess_ that this particular colon would be easily identifiable, but I
don't claim that. I have not looked at the code.

I asked if this was hard. You said it might be. I said that if it is too hard
then you will likely need to just move on. Dunno what more I can say. It is you
who estimates the difficulty, not I. It is you who decides whether to make this
enhancement.







  reply	other threads:[~2009-05-28 20:57 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
2009-05-28 18:24           ` Drew Adams
2009-05-28 20:40             ` martin rudalics
2009-05-28 20:57               ` Drew Adams [this message]
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

  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=B136BABA673B4A6DBF92B64E02E20CAA@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=3395@emacsbugs.donarmstrong.com \
    --cc=rudalics@gmx.at \
    /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).