unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jefferson Carpenter <jeffersoncarpenter2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: show-enclosing-scopes
Date: Sun, 3 Jun 2018 18:35:54 +0000	[thread overview]
Message-ID: <3bfafd57-7163-e3c6-5e4b-0324ed0c63cc@gmail.com> (raw)
In-Reply-To: <83efi9ibg7.fsf@gnu.org>

On 5/18/2018 9:02 AM, Eli Zaretskii wrote:
> Here, it flickers only in the scroll-bar area, and that is expected,
> since you delete the scopes window and then recreate it -- this has to
> redraw the scroll bar, and will necessarily flicker.

Updated so that it no longer deletes the window and re-creates it quite 
so many times - namely it no longer requires a pre-command-hook.

https://raw.githubusercontent.com/jeffersoncarpenter/emacs.d/master/show-enclosing-scope.el

> 
> Where does it flicker on your system?  And what OS is that, with what
> toolkit?

Good news, it doesn't flicker any more since I removed window deletion 
in the pre-command-hook.  In fact, there are no outstanding bugs as far 
as I know.

(The next step now is to make it more intelligent about what lines to 
show inside the minimap window.  Currently it does it purely based on 
indentation, which is not optimal in many cases.)

> 
> Btw, you have a bug in show-enclosing-scope--split-window: it doesn't
> call set-window-buffer on the "base window", so the fringe, and
> probably also the right margin (if it has to be non-empty) are not
> redrawn when the window is split.
> 

That's true -- don't tell anyone but I literally copied and pasted the 
code for creating and deleting the window from sublimity-mode, so I 
don't know if the code regarding margins and fringes is correct or not 
in my case.  I haven't had a problem with it, but I need to look into it.



  reply	other threads:[~2018-06-03 18:35 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                       ` show-enclosing-scopes Jefferson Carpenter
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                       ` Jefferson Carpenter [this message]
  -- 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=3bfafd57-7163-e3c6-5e4b-0324ed0c63cc@gmail.com \
    --to=jeffersoncarpenter2@gmail.com \
    --cc=eliz@gnu.org \
    --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).