From: Toru TSUNEYOSHI <t_tuneyosi@hotmail.com>
To: monnier@iro.umontreal.ca
Cc: emacs-devel@gnu.org
Subject: Re: linum.el: problem (bug ?) fix and improvement
Date: Sat, 14 May 2011 10:53:13 +0900 [thread overview]
Message-ID: <BLU0-SMTP106BB4F515AB64B292D5F48E28B0@phx.gbl> (raw)
In-Reply-To: <jwvfwoi60jb.fsf-monnier+emacs@gnu.org>
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: linum.el: problem (bug ?) fix and improvement
Date: Fri, 13 May 2011 13:26:04 -0300
Message-ID: <jwvfwoi60jb.fsf-monnier+emacs@gnu.org>
>>>> I have a case that I make unimportant text invisible temporarily, to
>>>> know only important information.
>>> Any reason why you don't use the ellipsis (see buffer-invisibility-spec)?
>> I can't check the ellipsis easily, if `truncate-lines' is non-nil and
>> the ellipsis text is truncated.
>
> Indeed, that can be a problem. Tho, if you make "foo\n" (as you seem to
> do) invisible, the "..." will end up at the beginning of the line rather
> than its end. So it'll probably be too visible rather than not enough.
>
Yes.
In that case, I would not use the ellipsis.
> BTW, making "\nfoo" invisible instead of "foo\n" should circumvent the
> current mis-numbering problem which your patch tries to circumvent.
>
Sorry, I am a little tired of trying.
>> (In this case, I must scroll the window horizontally many times.)
>
> C-e does the trick if you're on the right line.
>
I see.
(Although, the ellipsis is not always at the end of a line.
So I must scroll ...)
However, I still wish to know the invisibility information at a glance.
Currently, it is useful to check the result by `hide-sublevels' or
`hide-body' on `outline-minor-mode'.
>> If linum-mode provides information about the invisible text, I can check
>> the information very easily, I think.
>
> I understand that it makes sense in your particular case, but it seems
> too tightly linked to a particular use of invisible (and this particular
> use of invisible is in turn tightly linked to linum in order to make it
> bearable). So I'm not convinced this belongs in linum.el as it stands.
> OTOH maybe we could install a patch to linum.el that provides a hook
> that you could use to add the same functionality.
>
>
> Stefan
>
That's right.
(I will use the function for my own solution.)
Thank you.
prev parent reply other threads:[~2011-05-14 1:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 14:50 linum.el: problem (bug ?) fix and improvement Toru TSUNEYOSHI
2011-05-12 13:58 ` Stefan Monnier
2011-05-12 17:21 ` Eli Zaretskii
2011-05-12 19:43 ` Stefan Monnier
2011-05-13 12:14 ` Toru TSUNEYOSHI
2011-05-13 14:15 ` Stefan Monnier
2011-05-13 15:55 ` Toru TSUNEYOSHI
2011-05-13 16:26 ` Stefan Monnier
2011-05-14 1:53 ` Toru TSUNEYOSHI [this message]
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=BLU0-SMTP106BB4F515AB64B292D5F48E28B0@phx.gbl \
--to=t_tuneyosi@hotmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).