From: Dani Moncayo <dmoncayo@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: 10906@debbugs.gnu.org
Subject: bug#10906: 24.0.94; `c-mark-function' does set the mark well
Date: Mon, 5 Mar 2012 23:36:52 +0100 [thread overview]
Message-ID: <CAH8Pv0ijhC-WzUhf371nvHNeR0G8AZF1TrHSSXkenpWDB7bjWw@mail.gmail.com> (raw)
In-Reply-To: <20120305184133.GC2824@acm.acm>
On Mon, Mar 5, 2012 at 19:41, Alan Mackenzie <acm@muc.de> wrote:
>> > Any chance of a quick summary of how c-mark-function differs from
>> > mark-defun?
>
>> AFAIK, they differ at least in two things:
>
>> 1. `mark-defun' saves the original point location in the mark ring,
>> whereas `c-mark-function' does not. IMO, the point should be saved,
>> because in large defuns it may jump to a remote location and you may
>> want to return back to the original position. This bug report is
>> about this inconsistency, as you can see in the original post.
>
>> 2. Successive interactive invocations of `mark-defun' extend the
>> region to the next defuns (which I find useful), whereas
>> `c-mark-function' does not have this feature. Bug #5525 is a request
>> to remove this inconsistency, as you can see in the corresponding
>> thread.
>
>> >> Agreed, and BTW, if `c-mark-function' is going to be revised, please,
>> >> take also this problem into account:
>
>> >> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5525
>
> Here is a patch which should fix these problems. The logic around
> transient-mark-mode is somewhat complicated, so I would be grateful if
> you would check the patch does the Right Thing. I haven't amended the
> doc string yet. Thanks!
Thank you.
I've tried your patch, and it seems to work[*], at least with my usage
pattern, i.e., with `transient-mark-mode' enabled.
[*] Except for one thing:
- If you do `C-M-h' several times in a row until the mark reaches the
end of the file, the point ends up at the end of the region, and the
mark at the beginning (which doesn't seem right).
- If you try the same experiment with `mark-defun', the mark stays at
the end and the point at the start of the region (as expected).
--
Dani Moncayo
next prev parent reply other threads:[~2012-03-05 22:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 12:36 bug#10906: 24.0.94; `c-mark-function' does set the mark well Dani Moncayo
2012-02-29 9:02 ` Dani Moncayo
2012-03-01 21:24 ` Alan Mackenzie
2012-03-01 23:03 ` Dani Moncayo
2012-03-01 23:13 ` Alan Mackenzie
2012-03-03 14:16 ` Alan Mackenzie
2012-03-05 18:41 ` Alan Mackenzie
2012-03-05 22:36 ` Dani Moncayo [this message]
2012-03-07 21:09 ` Alan Mackenzie
2012-03-07 21:37 ` Dani Moncayo
2012-03-09 16:49 ` Alan Mackenzie
2012-03-01 23:16 ` Glenn Morris
2012-03-01 23:19 ` Glenn Morris
2012-03-08 11:51 ` bug#10906: Bug #10906 - " Alan Mackenzie
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=CAH8Pv0ijhC-WzUhf371nvHNeR0G8AZF1TrHSSXkenpWDB7bjWw@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=10906@debbugs.gnu.org \
--cc=acm@muc.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 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.