From: Filipe Silva <filipe.silva@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: relative line numbers and folding: how to make they play along?
Date: Wed, 13 Jul 2016 00:43:45 -0300 [thread overview]
Message-ID: <CAEwkUWOAShLbTthFrznsc5dK+qeaHSExh3-eC9KVx9rZchFdzw@mail.gmail.com> (raw)
In-Reply-To: <8360sbcvbz.fsf@gnu.org>
Is there a way, from emacs -Q, of setting relative line numbers as shown
here?
https://cloud.githubusercontent.com/assets/8352747/16707876/4bd64c22-45b5-11e6-8d13-ae9c994cbb02.png
On Tue, Jul 12, 2016 at 1:51 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Filipe Silva <filipe.silva@gmail.com>
> > Date: Mon, 11 Jul 2016 12:11:45 -0300
> >
> > there was some discussion in spacemacs about the relative line number
> > behaviour in emacs:
> > https://github.com/syl20bnr/spacemacs/issues/6536
> >
> > In essence, currently relative line numbers in emacs are rendered useless
> > if folding is applied to the buffer.
>
> What are "relative line numbers" in Emacs? I see nothing in these
> discussions that describes how (with what commands/packages) the line
> numbers were produced in Emacs. So it's hard to tell anything
> intelligent about this issue.
>
> > One of the spacemacs maintainers specifically said: "I should note that
> due
> > to how folding and line numbers work in Emacs this would be nigh
> impossible
> > to fix."
> > I find that difficult to believe given how people in emacs community
> praise
> > about emacs infinite extensibility.
>
> The right place and way to discuss this is by filing a bug report with
> all the specifics, including a recipe for reproducing the issue,
> preferably starting from "emacs -Q".
>
> Thanks in advance.
>
>
next prev parent reply other threads:[~2016-07-13 3:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 15:11 relative line numbers and folding: how to make they play along? Filipe Silva
2016-07-12 4:51 ` Eli Zaretskii
2016-07-13 3:43 ` Filipe Silva [this message]
2016-07-13 20:10 ` Stefan Monnier
2016-07-13 20:23 ` Eli Zaretskii
2016-07-13 22:33 ` Filipe Silva
2016-07-14 15:02 ` Eli Zaretskii
[not found] ` <mailman.1359.1468449224.26859.help-gnu-emacs@gnu.org>
2016-07-14 1:29 ` Dan Espen
2016-07-14 2:36 ` Stefan Monnier
2016-07-14 15:06 ` Eli Zaretskii
2016-07-14 15:55 ` Filipe Silva
2016-07-14 15:58 ` Filipe Silva
2016-07-14 16:12 ` Eli Zaretskii
2016-07-14 16:51 ` Filipe Silva
2016-07-14 18:23 ` Boris
2016-07-14 21:03 ` Stefan Monnier
2016-07-15 0:04 ` Filipe Silva
2016-07-15 0:18 ` Stefan Monnier
2016-07-15 0:41 ` Filipe
2016-07-15 7:07 ` Eli Zaretskii
2016-07-15 13:53 ` Stefan Monnier
2016-07-15 14:22 ` Eli Zaretskii
2016-07-15 14:54 ` Stefan Monnier
2016-07-15 15:34 ` Filipe Silva
[not found] ` <mailman.1414.1468511758.26859.help-gnu-emacs@gnu.org>
2016-07-15 2:02 ` Dan Espen
[not found] ` <mailman.1374.1468463825.26859.help-gnu-emacs@gnu.org>
2016-07-14 3:20 ` Rusi
2016-07-14 12:17 ` Stefan Monnier
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=CAEwkUWOAShLbTthFrznsc5dK+qeaHSExh3-eC9KVx9rZchFdzw@mail.gmail.com \
--to=filipe.silva@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).