all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: Somehow strange behaviour of `mark-sexp'
Date: Thu, 13 Feb 2014 11:02:32 -0500	[thread overview]
Message-ID: <barmar-D82983.11023213022014@news.eternal-september.org> (raw)
In-Reply-To: mailman.14952.1392303843.10748.help-gnu-emacs@gnu.org

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.

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.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***


       reply	other threads:[~2014-02-13 16:02 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 ` Barry Margolin [this message]
2014-02-13 16:22   ` Somehow strange behaviour of `mark-sexp' Thorsten Jolitz
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=barmar-D82983.11023213022014@news.eternal-september.org \
    --to=barmar@alum.mit.edu \
    --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.
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.