unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Somehow strange behaviour of `mark-sexp'
Date: Thu, 13 Feb 2014 17:22:29 +0100	[thread overview]
Message-ID: <8761ojx9ru.fsf@gmail.com> (raw)
In-Reply-To: barmar-D82983.11023213022014@news.eternal-september.org

Barry Margolin <barmar@alum.mit.edu> writes:

> In article <mailman.14952.1392303843.10748.help-gnu-emacs@gnu.org>,
>  Thorsten Jolitz <tjolitz@gmail.com> wrote:
>
>> Hi List, 
>> 
>> when doing 'C-h v mark-sexp' I see this (excerpt):
>> 
>> ,-----------------------------------------------------------------
>> | mark-sexp is an interactive compiled Lisp function in `lisp.el'.
>> | 
>> | It is bound to C-M-@, C-M-SPC.
>> `-----------------------------------------------------------------
>> 
>> Now, moving point to the beginning of C-M-@ and calling ` mark-sexp',
>> 
>> ,-----
>> | C-M-
>> `-----
>> 
>> is marked. When moving point to the @ at the end of C-M-@ and calling
>> `mark-sexp',
>> 
>> ,-----------
>> | @, C-M-SPC
>> `-----------
>> 
>> is marked, which I found a bit counter-intuitive.
>> 
>> PS 1
>> 
>> `forward-sexp' acts like that too
>> 
>> PS 2
>> 
>> I'm working on the console
>
> @, is part of backquote syntax, it unquotes the sexp following it. So it 
> thinks @, C-M-SPC is @, unquoting the variable C-M-SPC, and that's a 
> sexp.

Ok, I see. 


> I'm not sure why you would expect sensible behavior from a command 
> intended for dealing with Lisp code in the *Help* buffer, which is just 
> plain text.

not necessarily sensible behaviour, but mark-sexp works quite well on
all kinds of "things at point", so I probably like its useful behaviour
even in contexts outside its original scope. 

-- 
cheers,
Thorsten




  reply	other threads:[~2014-02-13 16:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.14952.1392303843.10748.help-gnu-emacs@gnu.org>
2014-02-13 16:02 ` Somehow strange behaviour of `mark-sexp' Barry Margolin
2014-02-13 16:22   ` Thorsten Jolitz [this message]
2014-02-13 20:15   ` Thorsten Jolitz
2014-02-13 15:04 Thorsten Jolitz

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=8761ojx9ru.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --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).