From: Jean Louis <bugs@gnu.support>
To: Drew Adams <drew.adams@oracle.com>
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>,
Eduardo Ochs <eduardoochs@gmail.com>
Subject: Re: [External] : Re: What can cause downcasing in Emacs Lisp code?
Date: Sat, 22 May 2021 00:00:24 +0300 [thread overview]
Message-ID: <YKgfaLC8TuapvRIy@protected.localdomain> (raw)
In-Reply-To: <SA2PR10MB4474B5BCA386AA73CF72EE1CF3299@SA2PR10MB4474.namprd10.prod.outlook.com>
* Drew Adams <drew.adams@oracle.com> [2021-05-21 23:43]:
> > During few months I found my sources downcased partially,
> > but if 30% downcased it seem as region was downcased, I
> > just don't remember marking that much of region.
>
> OK, here's the thing...
>
> `downcase-region' and some other commands that act on the
> region are _very old_. They predate even the existence of
> `transient-mark-mode', let alone the turning ON of that
> mode by default.
Could be. I have some key binding like C-c l and maybe I make mistake
and press C-x C-l -- but hooo. when I pressed it on this line without
region all line was downcased.
"when used as a command, the text between point and the mark is
operated on." -- which means my mark could be anywhere in the file,
and if i press c-x c-l anywhere down, without marked region, all the
text would be marked. That is what makes it invisible.
So that could be that, thank you Sherlock.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
Sign an open letter in support of Richard M. Stallman
https://stallmansupport.org/
prev parent reply other threads:[~2021-05-21 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 16:49 What can cause downcasing in Emacs Lisp code? Jean Louis
2021-05-20 17:21 ` Eduardo Ochs
2021-05-21 5:54 ` Jean Louis
2021-05-21 15:20 ` [External] : " Drew Adams
2021-05-21 15:45 ` Jean Louis
2021-05-21 16:01 ` Drew Adams
2021-05-21 20:05 ` Jean Louis
2021-05-21 20:42 ` Drew Adams
2021-05-21 21:00 ` Jean Louis [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=YKgfaLC8TuapvRIy@protected.localdomain \
--to=bugs@gnu.support \
--cc=drew.adams@oracle.com \
--cc=eduardoochs@gmail.com \
--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.
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).