unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package proposal: visual-path-abbrev.el
Date: Sun, 03 Mar 2019 16:52:56 +0100	[thread overview]
Message-ID: <87k1hg6jl3.fsf@gnu.org> (raw)
In-Reply-To: <83imx0f0x0.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 03 Mar 2019 17:11:23 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> However, there's a problem with the conditional 'display spec which
>> should in theory un-abbreviate the file name as soon as point enter's
>> the overlay's region.  Oftentimes that doesn't happen until I
>> explicitly force a redisplay with C-l or M-x.
>> 
>> Is there a good way to cope with that?
>
> Would it be possible for you to post a small test file that could be
> used to show-case this package, and where you see this problem?  I'd
> like to look into why that happens, and would appreciate a cooked test
> case for doing this.

You don't have to have a special file.  For me, this simple recipe did
the trick:

1. emacs -Q
2. M-x load-file RET visual-file-name-abbrev.el RET
3. M-x rgrep RET (defsubst RET *.el RET ~/Repos/el/emacs
4. In the *grep* buffer: M-x visual-file-name-abbrev-mode

As a result, the file names are indeed abbreviated but when I move up
and down using C-n/C-p, I'd expect the file name under point to be
displayed normally (so not the 'display spec but the normal text).  With
emacs -Q, the problem is even worse than with my usual config.  It seems
the conditional display spec is almost never tested, except when the
window is scrolled, but then usually after scrolling point is not on the
file name anymore which is now shown unabbreviated.

Bye,
Tassilo



  reply	other threads:[~2019-03-03 15:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02 11:05 [ELPA] New package proposal: visual-path-abbrev.el Tassilo Horn
2019-03-02 11:34 ` Eli Zaretskii
2019-03-02 14:59   ` Tassilo Horn
2019-03-03  9:46   ` Tassilo Horn
2019-03-03 13:48     ` Stefan Monnier
2019-03-03 15:11     ` Eli Zaretskii
2019-03-03 15:52       ` Tassilo Horn [this message]
2019-03-03 17:18         ` Eli Zaretskii
2019-03-03 17:55           ` Tassilo Horn
2019-03-04 18:03         ` Eli Zaretskii
2019-03-05 10:01           ` Tassilo Horn
2019-03-05 16:21             ` Eli Zaretskii
2019-03-05 18:32               ` Tassilo Horn
2019-03-08  5:49             ` Stefan Monnier
2019-03-08 14:02               ` Tassilo Horn
2019-03-08 17:34                 ` Tassilo Horn
2019-03-08 19:01                   ` Stefan Monnier
2019-03-08 22:18                     ` Stefan Monnier
2019-03-09  6:52                       ` Tassilo Horn
2019-03-08 18:52                 ` Stefan Monnier
2019-03-02 21:25 ` Leo Liu
2019-03-03  9:25   ` Tassilo Horn
2019-03-04  0:23     ` Leo Liu

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=87k1hg6jl3.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --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).