From: Alan Mackenzie <acm@muc.de>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 10906@debbugs.gnu.org
Subject: bug#10906: 24.0.94; `c-mark-function' does set the mark well
Date: Thu, 1 Mar 2012 23:13:41 +0000 [thread overview]
Message-ID: <20120301231341.GC19099@acm.acm> (raw)
In-Reply-To: <CAH8Pv0g6kcrP_h3656hXXZDPu3o3BQ4Pj_pYqLXN+BbOFYFmnA@mail.gmail.com>
On Fri, Mar 02, 2012 at 12:03:48AM +0100, Dani Moncayo wrote:
> > Hello, Dani.
> Hi Alan.
> >> > Regarding bug#10906, I think `c-mark-function' should be rewritten
> >> > to follow the logic of `mark-defun'.
> > 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
> > Again, what is this bug? Could you not even quote the title line from
> > it?
> I think this question is already answered.
Thanks!
> --
> Dani Moncayo
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2012-03-01 23:13 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 [this message]
2012-03-03 14:16 ` Alan Mackenzie
2012-03-05 18:41 ` Alan Mackenzie
2012-03-05 22:36 ` Dani Moncayo
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
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=20120301231341.GC19099@acm.acm \
--to=acm@muc.de \
--cc=10906@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
/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).