From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 43949@debbugs.gnu.org
Subject: bug#43949: Strange behaviour for linum-mode
Date: Mon, 12 Oct 2020 19:11:22 +0200 [thread overview]
Message-ID: <CAO48Bk92UJBTci5ZzT1uocep+Ca7EZgtbTCZFmsUbf4jGkGyqQ@mail.gmail.com> (raw)
In-Reply-To: <CADwFkm=EJ4Ft-3G2KcsxM5e_rVSVRBbMuf0jMu2ybhmtf=m7fQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 857 bytes --]
Hi Stefan, thanks for the suggestion.
It sort of works. However, only sort of. I miss the linum-format variable
and the linum face.
Maybe too many years in linum-mode
My linum settings look cool, don't they? ;-)
[image: image.png]
Best, /PA
On Mon, 12 Oct 2020 at 15:00, Stefan Kangas <stefan@marxist.se> wrote:
> Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>
> > emacs -Q <long file>
> >
> > select any theme with colours
> > M-x linum-mode
> > customize-variable linum-format to %05d
> > config to truncate long lines
> > Go to the end of a truncated line. The limun buffer disappears and is
> > replaced by blanks. IMHO, the linum buffer should no change
>
> Does this work better if you use display-line-numbers-mode instead?
>
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
[-- Attachment #1.2: Type: text/html, Size: 1593 bytes --]
[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 5552 bytes --]
next prev parent reply other threads:[~2020-10-12 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 11:48 bug#43949: Strange behaviour for linum-mode Pedro Andres Aranda Gutierrez
2020-10-12 13:00 ` Stefan Kangas
2020-10-12 17:11 ` Pedro Andres Aranda Gutierrez [this message]
2020-10-12 17:24 ` Robert Pluim
2020-10-13 5:33 ` Pedro Andres Aranda Gutierrez
2020-10-13 7:30 ` Robert Pluim
2020-10-13 15:46 ` Eli Zaretskii
2020-10-13 16:06 ` Robert Pluim
2020-10-13 16:19 ` Eli Zaretskii
2020-10-13 16:39 ` Robert Pluim
2020-10-13 16:58 ` Eli Zaretskii
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=CAO48Bk92UJBTci5ZzT1uocep+Ca7EZgtbTCZFmsUbf4jGkGyqQ@mail.gmail.com \
--to=paaguti@gmail.com \
--cc=43949@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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).