unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 10056@debbugs.gnu.org, Chong Yidong <cyd@gnu.org>
Subject: bug#10056: 24.0.91; `copy-to-register' does not deactivate the mark
Date: Fri, 3 Aug 2012 21:47:29 +0000	[thread overview]
Message-ID: <20120803214728.GA11675@acm.acm> (raw)
In-Reply-To: <CAH8Pv0gDvX7cz-xegAXCo+U9wHUn0jMU=hVpntiSr=jRQRONXg@mail.gmail.com>

Hi, Dani.

On Thu, Aug 02, 2012 at 12:07:06AM +0200, Dani Moncayo wrote:
> >> > As for c-indent-line-or-region, I have no opinion on that at all.

> >> (I'm CC-ing Alan.  Hopefully he has an opinion) This is the current
> >> behavior I observe:
> >> * If the command has to adjust the indentation of some line(s) in the
> >> region, the mark is deactivated at the end of the command.
> >> * Else, the mark is not deactivated.

> >> This behavior is definitely annoying for me: when I mark some fragment
> >> of code and type TAB, what I want is that Emacs revise the indentation
> >> of code, and correct it if necessary, but in any case, I don't want
> >> the mark to remain active.

> > Have you looked at the code for c-i-l-o-region? At a quick glance, I
> > can't see where the distinction is made between indentation adjusted and
> > not adjusted.  I don't actually use transient-mark-mode myself, so this
> > hasn't annoyed me one way or the other.

> > Is the distinction there for a reason, or did it just get there by
> > accident?  The defun is only several (as opposed to many) years old, so
> > the evidence should still be available in the bzr repo.

> I'm sorry, I (still) don't have enough knowledge of Emacs to delve
> into such questions.

> I reported this bug as a mere user, hoping that you (the maintainers),
> if agree with my reasoning, make the suitable changes to the program.

Sorry, misunderstanding on my part there.

> In the case at hand, what I reported is quite simple, I think: from
> "emacs -Q" (transient mark mode on) visit some C file, select some
> fragment of code and type TAB.

> Hopefully you'll see the same behavior as me:
> * If the code in the region was already well indented, nothing happens
> and the mark remains active.
> * Else, the code is indented and the mark is deactivated.

Yes, I see this.

> What I say is that the mark should be deactivated _always_ at the end
> of the command, because the "transient" operation (revise the
> indentation of those lines) is done.

> This is so obvious to me that I'm surprised of seeing you so
> hesitant...  but well, you decide :)

The hesitancy comes from long experience of Emacs; things which are so
obviously wrong to some are obviously the RT to others.  I was wondering
if this behaviour, strange though it seems to both of us, might have been
programmed deliberately.

In this case, there seems to be some bug at the lower levels of Emacs.
There is nothing in CC Mode I can find to explain this strange behaviour.
According to the elisp manual, the normal way of deactivating a region
when transient mark mode is enabled is to set the variable
`deactivate-mark', which instructs the command loop to do the business.

CC Mode doesn't set `deactivate-mark' at all.  Maybe some primitive does.
I don't really know transient-mark-mode.  Yidong, have you any
suggestions here?

> -- 
> Dani Moncayo

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2012-08-03 21:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 20:06 bug#10056: 24.0.91; `copy-to-register' does not deactivate the mark Dani Moncayo
2011-11-15 20:15 ` Dani Moncayo
2011-11-15 20:36   ` Dani Moncayo
2011-11-15 20:18 ` Dani Moncayo
2011-11-21  6:30 ` Chong Yidong
2012-06-05  7:44   ` Dani Moncayo
2012-07-28 19:01   ` Dani Moncayo
2012-07-29  4:45     ` Chong Yidong
2012-07-29  9:46       ` Dani Moncayo
2012-07-29  4:50     ` Chong Yidong
2012-07-29 10:01       ` Dani Moncayo
2012-08-01 21:17         ` Alan Mackenzie
2012-08-01 22:07           ` Dani Moncayo
2012-08-03 21:47             ` Alan Mackenzie [this message]
2012-09-08 20:21           ` Stefan Monnier
2012-09-09 20:20             ` Dani Moncayo
2012-09-11 14:42               ` Bastien
2012-12-05  8:04 ` bug#10056: 24.0.91; Mark deactivation Dani Moncayo
2012-12-08 10:09   ` Dani Moncayo
2012-12-08 23:03     ` Juri Linkov
2012-12-09  0:00       ` Drew Adams
2012-12-09  0:29         ` Juri Linkov
2012-12-09  3:21           ` Drew Adams
2012-12-09  9:07             ` Dani Moncayo
2013-01-25 12:34               ` Dani Moncayo
2013-01-25 17:41                 ` Drew Adams
2013-01-25 19:07                   ` Dani Moncayo
2013-01-25 19:34                     ` Drew Adams
2013-01-25 19:01                 ` Stefan Monnier
2022-04-26 13:50 ` bug#10056: 24.0.91; `copy-to-register' does not deactivate the mark Lars Ingebrigtsen

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=20120803214728.GA11675@acm.acm \
    --to=acm@muc.de \
    --cc=10056@debbugs.gnu.org \
    --cc=cyd@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).