unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Filipe Silva <filipe.silva@gmail.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Native display of line numbers
Date: Fri, 23 Jun 2017 08:17:45 -0300	[thread overview]
Message-ID: <CAEwkUWOZbhVkqwV2qAstFJxASeRVSqOyCjjGXWjs7Ef1vGRxyQ@mail.gmail.com> (raw)
In-Reply-To: <CAEwkUWNXtKYPpx-vQT_iPzRixMUDXCj2mDwEfFX2vq5Jpc0JdQ@mail.gmail.com>

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

by the way, that's the way emacs with evil-mode handles things right now.

d9j will delete every VISUAL line, and if any of those visual lines are
actually collapsed, the entire set of real lines will be killed in the
process.

Exciting stuff. now we just need that relative line numbers feature out to
be able to shred text in emacs with even more power.

gogo Eli! :)

Filipe


On Fri, Jun 23, 2017 at 8:10 AM, Filipe Silva <filipe.silva@gmail.com>
wrote:

> when deleting 9 lines below with d9j, vim works in terms of visual lines.
>
> so if you have, between those visual lines, a line that represents a
> collapsed org-mode buffer that has a thousand lines beneath it, it would
> kill those lines in the process.
>
> That's what I'd expect. I'm killing what I'm seeing. I know that it is a
> collapsed org-mode buffer bullet. I'm deleting 9 lines below of the current
> line. I want that org-mode buffer collapsed buffer to be killed to.
>
> If you want to delete the real lines, just expand the bullet.
>
> as I said, you can see that this is hugely powerful.
>
>
>
> On Thu, Jun 22, 2017 at 1:27 PM, Yuri Khan <yuri.v.khan@gmail.com> wrote:
>
>> On Thu, Jun 22, 2017 at 10:02 PM, Filipe Silva <filipe.silva@gmail.com>
>> wrote:
>>
>>
>> > Vim implements relative line numbers in a way that the "relativity"
>> aspect
>> > is based on the visible lines of the buffer.
>>
>> > Why this is useful? because it gives vim/evil-mode users the power to
>> > rapidly move through the visible lines in the window. If I want to jump
>> to a
>> > line in the buffer that I'm interested in, I just have to take a peek
>> at the
>> > relative number and then I know what to do. I just: 9k, to jump 9 lines
>> > down. This is actually super powerful.
>>
>> What about deleting 9 lines? Does deletion work in terms of visual or
>> logical lines in vim?
>>
>> In Emacs, as far as I can tell, visual line movement only affects
>> movement, killing still works by logical lines.
>>
>> That may mean you’d need relative visual line numbers when you are
>> going to press a movement (<up>/<down>/C-n/C-p) key, and relative
>> logical line numbers when you are going to press a kill-line key
>> (<C-S-backspace> or C-k).
>>
>
>

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

  reply	other threads:[~2017-06-23 11:17 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-17 15:12 Native display of line numbers Eli Zaretskii
2017-06-17 16:41 ` Stefan Monnier
2017-06-17 18:25   ` Eli Zaretskii
2017-06-17 21:25     ` Stefan Monnier
2017-06-18 14:21       ` Eli Zaretskii
2017-06-17 16:52 ` Kaushal Modi
2017-06-17 17:20   ` Kaushal Modi
2017-06-17 17:42     ` Eli Zaretskii
2017-06-17 17:41   ` Eli Zaretskii
2017-06-17 21:16     ` Stefan Monnier
2017-06-18  4:27     ` Kaushal Modi
2017-06-18 14:40       ` Eli Zaretskii
2017-06-17 20:27 ` Alan Mackenzie
2017-06-17 21:26   ` Stefan Monnier
2017-06-18  2:35   ` Eli Zaretskii
2017-06-18 11:42     ` Alan Mackenzie
2017-06-18 12:16       ` Colin Baxter
2017-06-18 15:06       ` Eli Zaretskii
2017-06-18 15:47         ` Alan Mackenzie
2017-06-18 16:11           ` Eli Zaretskii
2017-06-18 20:19             ` Alan Mackenzie
2017-06-19  2:28               ` Eli Zaretskii
2017-06-17 20:47 ` Sébastien Le Callonnec
2017-06-18  2:38   ` Eli Zaretskii
2017-06-18 10:51     ` Sébastien Le Callonnec
2017-06-17 21:32 ` Mathias Dahl
2017-06-17 22:12   ` James Nguyen
2017-06-18 14:31     ` Eli Zaretskii
2017-06-19  2:25       ` James Nguyen
2017-06-19 15:32         ` Eli Zaretskii
2017-06-19 16:33           ` James Nguyen
2017-06-18 14:28   ` Eli Zaretskii
2017-06-18 14:42     ` Andreas Schwab
2017-06-18  8:44 ` martin rudalics
2017-06-18  8:58   ` martin rudalics
2017-06-18 14:46   ` Eli Zaretskii
2017-06-19  2:39     ` Eli Zaretskii
2017-06-19  8:04       ` martin rudalics
2017-06-19 15:13         ` Eli Zaretskii
2017-06-18 11:03 ` Yuri Khan
2017-06-18 14:54   ` Eli Zaretskii
2017-06-18 16:54     ` Yuri Khan
2017-06-18 19:00       ` Eli Zaretskii
2017-06-19  5:32         ` Yuri Khan
2017-06-19 15:51           ` Eli Zaretskii
2017-06-24 10:32     ` Eli Zaretskii
2017-06-18 19:41 ` Daniele Nicolodi
2017-06-18 20:04   ` Eli Zaretskii
2017-06-18 20:48     ` Daniele Nicolodi
2017-06-19  2:31       ` Eli Zaretskii
2017-06-19  3:07         ` Daniele Nicolodi
2017-06-19 15:03           ` Eli Zaretskii
2017-06-19  2:44       ` Clément Pit-Claudel
2017-06-19  4:15         ` Eli Zaretskii
2017-06-19  4:30           ` Clément Pit-Claudel
2017-06-18 22:20 ` Scott Jaderholm
2017-06-19  2:34   ` Eli Zaretskii
2017-06-19  5:49     ` Scott Jaderholm
2017-06-19 16:56 ` Stephen Leake
2017-06-19 17:11   ` Eli Zaretskii
2017-06-19 18:43     ` Stephen Leake
2017-06-19 19:32       ` Eli Zaretskii
2017-06-19 18:39 ` Alan Mackenzie
2017-06-19 19:28   ` Eli Zaretskii
2017-06-19 19:38     ` Alan Mackenzie
2017-06-19 19:51       ` Eli Zaretskii
2017-06-22 15:02 ` Filipe Silva
2017-06-22 15:38   ` Eli Zaretskii
2017-06-22 15:46     ` Filipe Silva
2017-06-23 16:23     ` Stefan Monnier
2017-06-23 21:04       ` Eli Zaretskii
2017-06-23 21:24         ` Stefan Monnier
2017-06-24  7:18           ` Eli Zaretskii
2017-06-22 16:27   ` Yuri Khan
2017-06-22 16:56     ` Stephen Berman
2017-06-23 11:10     ` Filipe Silva
2017-06-23 11:17       ` Filipe Silva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-06-17 23:44 Joseph Garvin

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=CAEwkUWOZbhVkqwV2qAstFJxASeRVSqOyCjjGXWjs7Ef1vGRxyQ@mail.gmail.com \
    --to=filipe.silva@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yuri.v.khan@gmail.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).