From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Stefan Kangas <stefan@marxist.se>
Cc: "16196@debbugs.gnu.org" <16196@debbugs.gnu.org>,
"Jan Djärv" <jan.h.d@swipnet.se>,
"Stefan Monnier" <monnier@iro.umontreal.ca>
Subject: bug#16196: 24.3.50; Disable ding when scrolling
Date: Sun, 11 Aug 2019 17:28:17 +0300 [thread overview]
Message-ID: <87lfvzn5dq.fsf@tcd.ie> (raw)
In-Reply-To: <CADwFkm=VRsRe65zQOmxDFDeN1LGC44GiZJUszrzxRdEt1ds1TQ@mail.gmail.com> (Stefan Kangas's message of "Sat, 10 Aug 2019 20:07:29 +0200")
Stefan Kangas <stefan@marxist.se> writes:
> Basil L. Contovounesios <contovob@tcd.ie> writes:
>> FWIW, you can slightly reduce the amount of code that needs reindenting
>> by binding saw-error in the existing let* form:
>
> Sure, I could've done that, but I was worried that moving the final sexp in that
> defun into the let* form would cause a regression. It might have been left
> outside for a purpose. (Or it could just be that it didn't need to be in the
> let* form before.)
It looks like the latter:
Avoid accidental yanking of text while scrolling with the mouse wheel.
d09696f73f 2002-11-28 23:03:30 +0000
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=d09696f73f17c4ae0bf09e8c72ef7f427f07d31b
> Are you saying that you know that it's safe to move it?
Inasmuch as I can "know" something about a code fragment from just
looking at it, yes. Note that this does not mean I am urging you to
move it; I merely suggested it as a stylistic alternative or tip,
"FWIW".
Thanks,
--
Basil
next prev parent reply other threads:[~2019-08-11 14:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 6:08 bug#16196: 24.3.50; Disable ding when scrolling Jan Djärv
2013-12-20 8:56 ` Eli Zaretskii
2013-12-20 10:26 ` Jan Djärv
2013-12-20 10:32 ` Jan Djärv
2013-12-20 10:48 ` Eli Zaretskii
2013-12-20 17:52 ` Jan Djärv
2013-12-20 18:10 ` Eli Zaretskii
2013-12-20 18:48 ` Jan Djärv
2013-12-20 20:35 ` Eli Zaretskii
2013-12-23 2:46 ` Stefan Monnier
2013-12-23 10:44 ` Jan Djärv
2014-01-03 22:57 ` Stefan Monnier
2014-01-03 23:46 ` Jan Djärv
2014-01-04 0:03 ` Drew Adams
2014-01-04 5:07 ` Stefan Monnier
2014-01-04 9:40 ` Jan Djärv
2014-01-04 13:43 ` martin rudalics
2014-01-04 20:40 ` Stefan Monnier
2014-01-04 7:25 ` Eli Zaretskii
2014-01-04 9:36 ` Jan Djärv
2013-12-20 10:43 ` Eli Zaretskii
2019-08-09 7:55 ` Stefan Kangas
2019-08-09 8:57 ` Basil L. Contovounesios
2019-08-10 18:07 ` Stefan Kangas
2019-08-11 14:28 ` Basil L. Contovounesios [this message]
2019-08-12 0:52 ` Stefan Kangas
2019-09-30 13:26 ` Stefan Kangas
2019-09-30 13:55 ` Eli Zaretskii
2019-09-30 14:03 ` Robert Pluim
2019-09-30 14:11 ` Robert Pluim
2019-09-30 14:19 ` Stefan Kangas
2019-09-30 21:51 ` Stefan Kangas
2019-10-04 16:11 ` Stefan Kangas
2019-08-09 9:00 ` martin rudalics
2019-08-10 18:23 ` Stefan Kangas
2019-08-11 8:17 ` martin rudalics
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=87lfvzn5dq.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=16196@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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).