Hacker News Reader

Comment by astine | Hacker News Reader

Trivial counter-example:

  .some-css-rule { padding-left:50px; padding-right:50px; margin:50px; }

Pretend you want to avoid changing the margin.

View on HN

:s/50/60/g<CR> @:

or even just /50<CR>r6n.

if there's any new feature I'd like to see in neovim it would be one key that will repeat an ex command like period does for normal/visual mode

You're first example wont work. What you want is

    :s/50/60/<CR> @:

And that still won't handle

    .some-css-rule { margin:50px;  padding-left:50px; padding-right:50px; }

The second example will work, for this, but not for the situation where you change your mind halfway through and decide you want 70px instead.

Glib response:

:s/t:50/t:60/g

More serious response: I think after many years of training ones brain to use the features available to it some of those features become second nature and subconscious. This is great for editing and it's the reason I immediately saw that you left me a really easy way to do it, but it can make seeing the value of new features more difficult.

How about this one:

    .some-css-rule { padding-left:50px; padding-right:50px; margin-left:50px; margin-right:50px; }

I run into examples like this a lot and have yet to find an elegant way to deal with it. Honestly, I'd like to see if there's a simple solution.

I find that I spend a lot of time in my editor crafting regular expressions to do clever replacements and I've yet to get so good at it that it doesn't distract me from my editing.

Reply on news.ycombinator.com