unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jefferson Carpenter <jeffersoncarpenter2@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: show-enclosing-scopes
Date: Fri, 18 May 2018 06:26:55 +0000	[thread overview]
Message-ID: <abf7537e-2fb7-4dd6-d41b-55bffac43ced@gmail.com> (raw)
In-Reply-To: <8f2e1f29-caed-8565-3101-69d26e240d36@gmail.com>

-Pickles

On 5/18/2018 6:18 AM, Jefferson Carpenter wrote:
> On 5/18/2018 6:02 AM, Jefferson Carpenter wrote:> Also, 
> (recenter-top-bottom) is behaving really bizarrely now.  I'll have
>> to look into that.
> 
> I do think it would make sense for as many state changes as possible to 
> happen during command execution, pending a redisplay once execution has 
> completely finished.  (redisplay) shall not have to be added after 
> (scroll-up) and (scroll-down) in order to set point subsequently, and 
> functions that recenter point, alter the number of open windows, and so 
> on, don't needlessly redisplay the buffer while synchronous elisp code 
> is executing.
> 
> Pickles,
> Jefferson



  reply	other threads:[~2018-05-18  6:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16  6:41 show-enclosing-scopes Jefferson Carpenter
2018-05-16  8:03 ` show-enclosing-scopes Eli Zaretskii
2018-05-16 21:46   ` show-enclosing-scopes Jefferson Carpenter
2018-05-17 14:31     ` show-enclosing-scopes Stefan Monnier
2018-05-17 15:07       ` show-enclosing-scopes Eli Zaretskii
2018-05-17 17:41         ` show-enclosing-scopes Stefan Monnier
2018-05-17 19:16           ` show-enclosing-scopes Eli Zaretskii
2018-05-17 20:24             ` show-enclosing-scopes Stefan Monnier
2018-05-18  1:13               ` show-enclosing-scopes Jefferson Carpenter
2018-05-18  1:16                 ` show-enclosing-scopes Jefferson Carpenter
2018-05-18  6:15                   ` show-enclosing-scopes Eli Zaretskii
2018-05-18  2:22                 ` show-enclosing-scopes Stefan Monnier
2018-05-18  6:02                   ` show-enclosing-scopes Jefferson Carpenter
2018-05-18  6:18                     ` show-enclosing-scopes Jefferson Carpenter
2018-05-18  6:26                       ` Jefferson Carpenter [this message]
2018-05-18  7:01                       ` show-enclosing-scopes Eli Zaretskii
2018-05-18  8:46                     ` show-enclosing-scopes Eli Zaretskii
2018-05-19  4:17                       ` show-enclosing-scopes Jefferson Carpenter
2018-05-19  8:38                         ` show-enclosing-scopes Eli Zaretskii
2018-05-21  3:31                           ` show-enclosing-scopes Jefferson Carpenter
2018-05-25  7:07                             ` show-enclosing-scopes Jefferson Carpenter
2018-05-18  9:02                     ` show-enclosing-scopes Eli Zaretskii
2018-06-03 18:35                       ` show-enclosing-scopes Jefferson Carpenter
  -- strict thread matches above, loose matches on Subject: below --
2018-05-16  6:40 show-enclosing-scopes Jefferson Carpenter

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=abf7537e-2fb7-4dd6-d41b-55bffac43ced@gmail.com \
    --to=jeffersoncarpenter2@gmail.com \
    --cc=emacs-devel@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.
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).