unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Carlos Pita <carlosjosepita@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32337@debbugs.gnu.org
Subject: bug#32337: 26.1; display-line-numbers-mode makes cursor ill-aligned when number face is changed
Date: Wed, 1 Aug 2018 09:03:54 -0300	[thread overview]
Message-ID: <CAELgYhfVNPF+uE9fm0+movazOvUAJwSkvYqmjeE8yqY3Z=PzAw@mail.gmail.com> (raw)
In-Reply-To: <83y3dqmhkl.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 553 bytes --]

I meant as a pseudo line-number so that the line-number face geometry is
used.

On Wed, Aug 1, 2018, 8:50 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Carlos Pita <carlosjosepita@gmail.com>
> > Date: Wed, 1 Aug 2018 07:33:07 -0300
> > Cc: 32337@debbugs.gnu.org
> >
> > And what about showing the eof unicode glyph, it's just one character so
> it can't affect width calculations and
> > it's a useful indicator that says "there is really nothing here".
>
> Showing it where?
>
> We already have an EOB indication, see indicate-buffer-boundaries.
>

[-- Attachment #2: Type: text/html, Size: 1018 bytes --]

  reply	other threads:[~2018-08-01 12:03 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 19:19 bug#32337: 26.1; display-line-numbers-mode makes cursor ill-aligned when number face is changed Carlos Pita
2018-07-31 19:26 ` Carlos Pita
2018-08-01  7:48   ` Eli Zaretskii
2018-08-01 10:33     ` Carlos Pita
2018-08-01 10:38       ` Carlos Pita
2018-08-01 11:50       ` Eli Zaretskii
2018-08-01 12:03         ` Carlos Pita [this message]
2018-08-01 12:09           ` Eli Zaretskii
2018-08-01 12:31             ` Carlos Pita
2018-08-01 12:34               ` Eli Zaretskii
2018-08-02  2:08                 ` Richard Stallman
2018-08-02 23:06                   ` Carlos Pita
2018-08-03  6:03                     ` Eli Zaretskii
2018-08-03 18:40                       ` Carlos Pita
2018-08-03 23:14                         ` Carlos Pita
2018-08-04  6:29                           ` Eli Zaretskii
2018-08-04  7:07                             ` Eli Zaretskii
2018-08-07 17:12                               ` Carlos Pita
2018-08-31 12:10                                 ` Carlos Pita
2018-09-01 13:39                                   ` Eli Zaretskii
2018-09-01 14:50                                     ` Carlos Pita
2018-09-07  7:53                                       ` Eli Zaretskii
2018-09-25 19:27                                         ` Carlos Pita
2018-09-25 19:40                                           ` Carlos Pita
2018-09-25 19:54                                             ` Eli Zaretskii
2018-09-25 20:00                                               ` Carlos Pita
2018-09-25 19:46                                           ` Eli Zaretskii
2018-09-25 19:52                                             ` Carlos Pita
2018-09-26 15:39                                             ` Eli Zaretskii
2018-09-26 16:16                                               ` Carlos Pita
2018-09-26 19:20                                                 ` Eli Zaretskii
2018-10-10 18:33                                                   ` Carlos Pita
2018-10-13  6:46                                                     ` Eli Zaretskii
     [not found]                                                       ` <CAELgYhceFMmTc=G3VY6rmHKsk+g5upsM_n7w1xvjU-dvf7ZYYA@mail.gmail.com>
2019-02-19 15:26                                                         ` Carlos Pita
2019-02-19 15:27                                                           ` Carlos Pita
2019-02-19 16:57                                                         ` Eli Zaretskii
2019-02-19 20:01                                                           ` Carlos Pita
2019-02-19 22:38                                                             ` Carlos Pita
2018-08-01  7:47 ` 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='CAELgYhfVNPF+uE9fm0+movazOvUAJwSkvYqmjeE8yqY3Z=PzAw@mail.gmail.com' \
    --to=carlosjosepita@gmail.com \
    --cc=32337@debbugs.gnu.org \
    --cc=eliz@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).