unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: xah lee <xah@xahlee.org>
To: Alan Mackenzie <acm@muc.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: bug#1406: backward-up-list reports scan error incorrectly?
Date: Thu, 27 Nov 2008 07:56:17 -0800	[thread overview]
Message-ID: <FE629FAA-6C60-4633-BA43-D2D4F61B2FF9@xahlee.org> (raw)
In-Reply-To: <20081127121951.GA3137@muc.de>

On Nov 27, 4:19 am, Alan Mackenzie <a...@muc.de> wrote:
 > Hi, Xah!
 >
 > > > though, isn't this something easy to fix?
 > > No, because it isn't a bug.  It's the way the function is meant  
to work.
 > > If there is a bug, it's that the doc-string (and maybe the elisp  
manual,
 > > I haven't looked) is vague and incomplete.
 >
 > I've amended the Emacs manual (.../doc/emacs/programs.texi) and  
the doc
 > strings of `backward-up-list' and several similar functions
 > (.../lisp/emacs-lisp/lisp.el).
 >
 > If you're interested, have a look at the changes in
 > <http://cvs.savannah.gnu.org/viewvc/emacs/?root=emacs>.

Thanks Alan.

I'd rather hope for a fix instead of change wording to reflect  
current situation.

You argued in bug list that the issue is not simple essentially due  
to the fact that straight quote chars are not matching pairs.

That is true, but i think given today's tech and computing power, we  
can over come this. Just assume that double quotes in the source code  
are matched, since they are most of the time. In the few cases when  
the backward-up-list went to the wrong place due to un-matched double  
quote, i think that's ok. (as opposed to, it stops dead and utter a  
beep.)

alternatively, if the cursor is inside double quote, then issue a  
warning in the messag area that the result may not be correct.

Also, since this works in text-mode, so apparently this can work. A  
implementation is to temporarily switch to that mode, do the cursor  
move, then switch back. Or temp set the syntax table to whatever chat  
that made text-mode work and emacs-lisp-mode not work.

In general, my feeling is that moving around nested pairs is not a  
some insurmountable issue, that given today's technology and  
software, it seems wimpy to tell users that backward-up-list won't  
work if it's inside double quotes. Much complex problems are solved  
today in emacs, in other IDEs, etc.

Just my opinions. Thanks.

   Xah
∑ http://xahlee.org/

☄



On Nov 27, 2008, at 4:19 AM, Alan Mackenzie wrote:

Hi, Xah!

>> though, isn't this something easy to fix?

> No, because it isn't a bug.  It's the way the function is meant to  
> work.
> If there is a bug, it's that the doc-string (and maybe the elisp  
> manual,
> I haven't looked) is vague and incomplete.

I've amended the Emacs manual (.../doc/emacs/programs.texi) and the doc
strings of `backward-up-list' and several similar functions
(.../lisp/emacs-lisp/lisp.el).

If you're interested, have a look at the changes in
<http://cvs.savannah.gnu.org/viewvc/emacs/?root=emacs>.

-- 
Alan Mackenzie (Nuremberg, Germany).

☄






  reply	other threads:[~2008-11-27 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EAA45A2E-4CC6-4F13-863A-9A934FF60165@xahlee.org>
     [not found] ` <20081121231944.GB2089@muc.de>
     [not found]   ` <5F3AB054-C158-4518-9C93-6938EB2D123D@xahlee.org>
     [not found]     ` <20081122123644.GA3330@muc.de>
     [not found]       ` <12CBE034-485F-49CE-9EF6-2C33A51AF0C1@xahlee.org>
     [not found]         ` <9331FB10-71C6-4B1B-94B6-B5C9B3667B74@xahlee.org>
     [not found]           ` <20081122140446.GC3330@muc.de>
2008-11-27 12:19             ` bug#1406: backward-up-list reports scan error incorrectly? Alan Mackenzie
2008-11-27 15:56               ` xah lee [this message]
2008-11-27 22:09                 ` Alan Mackenzie
2008-11-27 22:49                   ` xah lee
     [not found]             ` <mailman.1345.1227787599.26697.help-gnu-emacs@gnu.org>
2008-11-27 15:52               ` Xah Lee

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=FE629FAA-6C60-4633-BA43-D2D4F61B2FF9@xahlee.org \
    --to=xah@xahlee.org \
    --cc=acm@muc.de \
    --cc=help-gnu-emacs@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.
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).