unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eduardo Ochs <eduardoochs@gmail.com>
To: Jean Louis <bugs@gnu.support>
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Re: What can cause downcasing in Emacs Lisp code?
Date: Thu, 20 May 2021 14:21:24 -0300	[thread overview]
Message-ID: <CADs++6hFzo98HvcvLfa9n+AvJ7FPor_zrvWbaS2S39X=gqEPpg@mail.gmail.com> (raw)
In-Reply-To: <courier.0000000060A6932D.0000108B@stw1.rcdrun.com>

Do you type `M-l', a.k.a., `downcase-word', by accident often? I do =/...

On Thu, 20 May 2021 at 13:50, Jean Louis <bugs@gnu.support> wrote:
>
> I have noticed few times in last months, including today, that I find
> some strings in Emacs Lisp code downcased. I cannot know what is
> happening, as it is maybe something I press by mistake, but I cannot
> find what. I don't mark things and don't use `downcase-region'
>
> As usually all of the Emacs Lisp is anyway downcased, I can only
> observe strings within quotes to be downcased, but maybe some
>
> Then I can observe instead of this:
>
> (defun hlink-yank-note (&optional id)
>   "Kill the note and yanks into the other window"
>   (interactive)
>   (when-tabulated-id "hlinks" id
>     (hyperscope-ring id)
>     (hlink-yank-note-1 id)))
>
> I can observe following "kill" instead of "Kill"
>
> (defun hlink-yank-note (&optional id)
>   "kill the note and yanks into the other window"
>   (interactive)
>   (when-tabulated-id "hlinks" id
>     (hyperscope-ring id)
>     (hlink-yank-note-1 id)))
>
> And that downcasing makes me again edit so much more. I do not know
> how I invoke that.
>
> Maybe somebody knows?
>
>
>
> Jean
>



  reply	other threads:[~2021-05-20 17:21 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 [this message]
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

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='CADs++6hFzo98HvcvLfa9n+AvJ7FPor_zrvWbaS2S39X=gqEPpg@mail.gmail.com' \
    --to=eduardoochs@gmail.com \
    --cc=bugs@gnu.support \
    --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).