unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Unify mark-foo commands
Date: Fri, 15 Feb 2002 10:23:19 +0100	[thread overview]
Message-ID: <vaf664z9jzs.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <vafn0yixzez.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@cs.uni-dortmund.de's message of "Sat, 09 Feb 2002 19:50:28 +0100")

Kai.Grossjohann@cs.uni-dortmund.de (Kai Großjohann) writes:

> The mark-sexp command recently acquired the (very nifty) feature that
> repeating the command extends the selection (so C-M-SPC C-M-SPC marks
> two sexps).
>
> WIBNI the other mark-foo commands behaved similarly?

I have now committed the patch that does this.  To be specific:

* mark-sexp has been changed so that it doesn't push a second mark
  when hitting C-M-SPC the second time.  Instead, the first mark is
  moved.

* mark-word now does the same as mark-sexp, more or less.

* mark-defun and mark-paragraph also support the extension feature,
  but these two still push multiple marks.  (I didn't know how to turn
  that off, and I don't think it's a really serious problem.)

I hope that this was the right thing to do.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


      parent reply	other threads:[~2002-02-15  9:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-09 18:50 Unify mark-foo commands Kai Großjohann
2002-02-11  2:09 ` Richard Stallman
2002-02-13 16:52   ` Kai Großjohann
2002-02-14 12:46     ` Richard Stallman
2002-02-14 13:15       ` Kai Großjohann
2002-02-14  9:04   ` Kai Großjohann
2002-02-14 10:13     ` Eli Zaretskii
2002-02-15 10:36     ` Richard Stallman
2002-02-15 10:36     ` Richard Stallman
2002-02-15  9:23 ` Kai Großjohann [this message]

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=vaf664z9jzs.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).