From: Ergus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34513@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#34513: display-line-numbers in term mode
Date: Mon, 21 Oct 2019 23:44:11 +0200 [thread overview]
Message-ID: <20191021214411.mxmsoptcdppamhlf@Ergus> (raw)
In-Reply-To: <838spe4mm4.fsf@gnu.org>
On Mon, Oct 21, 2019 at 09:51:47AM +0300, Eli Zaretskii wrote:
>> Date: Mon, 21 Oct 2019 00:54:46 +0200
>> From: Ergus <spacibba@aol.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
>>
>> I have tried the quick solution Stefan proposed to this but there are
>> still limitations when the number column width change and some
>> others when resizing the window. Does anyone has a way to improve
>> this?
>
>You can see the various solutions in tabulated-list.el. I wrote them
>because features like package.el need to react to the changing width
>of the line numbers.
>
>In addition to the change in the line numbers display width due to
>scrolling, there are changes due to resizing the default font.
>
Hi Eli:
I see that, but what about when the window width changes? Are there any
hook we ca use?
>> On the other hand I wanted to ask if new changes like dfci must be
>> disabled in term-mode by default or we let that configuration to the
>> user?
>
>This is a different issue, unrelated to this bug report. Let's
>discuss it separately, probably on emacs-devel.
>
>Thanks.
next prev parent reply other threads:[~2019-10-21 21:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 14:19 bug#34513: display-line-numbers in term mode Ergus
2019-02-27 15:26 ` Stefan Monnier
2019-02-27 16:05 ` Eli Zaretskii
2019-02-27 16:40 ` Stefan Monnier
2019-02-27 17:06 ` Eli Zaretskii
2019-02-27 17:21 ` Stefan Monnier
2019-02-27 17:33 ` Eli Zaretskii
[not found] ` <<831s3tkufj.fsf@gnu.org>
2019-02-27 18:00 ` Drew Adams
2019-02-27 18:20 ` Eli Zaretskii
[not found] ` <<<831s3tkufj.fsf@gnu.org>
[not found] ` <<9f8f0712-1187-4ce3-bd2c-af44cf00927d@default>
[not found] ` <<83wolljdpe.fsf@gnu.org>
2019-02-27 19:04 ` Drew Adams
2020-09-20 18:30 ` Lars Ingebrigtsen
2020-09-20 18:50 ` Eli Zaretskii
2020-09-20 19:56 ` Lars Ingebrigtsen
2020-09-21 2:27 ` Eli Zaretskii
2020-09-21 14:10 ` Lars Ingebrigtsen
2019-02-27 17:46 ` bug#34513: Fwd: " Ergus
2019-02-27 18:15 ` Eli Zaretskii
2019-10-20 22:54 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-10-21 6:51 ` Eli Zaretskii
2019-10-21 21:44 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2019-10-22 15:11 ` Eli Zaretskii
[not found] <8736fkaish.fsf@aol.com>
2019-10-22 17:33 ` Eli Zaretskii
2019-10-22 23:06 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-10-23 16:21 ` Eli Zaretskii
2019-10-23 16:50 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=20191021214411.mxmsoptcdppamhlf@Ergus \
--to=bug-gnu-emacs@gnu.org \
--cc=34513@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=spacibba@aol.com \
/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).