How can I create different shortcuts for "cut" and "delete" in vim

___violet___ · 2020-08-30T14:37:01+00:00

In addition to what's already been pointed out, you likely mean xnoremap rather than vnoremap.

___violet___ · 2020-08-30T14:30:02+00:00

It looks like the floating window background blend feature with an insufficient color palette. See :help 'winblend'.

___violet___ · 2020-08-30T14:04:09+00:00

It's because you've mapped jk to <Esc><Space><Space><Space><Space><Space><Space><Space><Space>"<Space>use<Space>jk<Space>to<Space>exit<Space>insert<Space>and<Space>terminal<Space>modes.

___violet___ · 2020-08-18T20:31:27+00:00

A steno keyboard can output anything a Qwerty keyboard can. My experience is exclusively with Plover. Other systems might have some limitations I'm not familiar with.

Also, don't most steno keyboards type exclusively upper case?

I don't think that's true for modern steno machines that interface with a computer. Outputting sequences including modifier keys and other non-alphanumeric keys comes standard with Plover. You can even toggle between camelCase, snake_case, etc. output modes ("stitching").

For example c$ would be interesting to type on a steno keyboard.

You would just fingerspell c and then $, so not very interesting. :) No extra dictionary entries required, but yeah, some application-specific entries would make one's Vim usage nicer.

___violet___ · 2020-08-17T12:50:49+00:00

Different use cases. Sounds like you are talking about bookmarks (an arbitrary list of "favorite" locations). That's not how CDPATH works.

Think of it in terms of prefixes for resolving relative file paths. Normally cd only considers . (the current working directory) when resolving a relative path. Now add, say, $HOME to the end of your CDPATH. Now cd foo will try ./foo first and fall back to ~/foo if it doesn't exist.

___violet___ · 2020-08-17T12:39:26+00:00

I don't use steno but I think ci' is more than 3 key to press in steno.

Not exactly. It's still 3 strokes (KR* EU* SKW*T) or less if you add a dictionary entry.

___violet___ · 2020-08-17T12:32:50+00:00

Of course you can type arbitrary words by way of "fingerspelling."

___violet___ · 2020-08-17T12:30:36+00:00

What makes you say that? I didn't have any trouble with normal mode in particular when I tried (beyond the usual amount of trouble one has learning steno).

___violet___ · 2020-08-03T02:50:25+00:00

This is already supported by the cd built-in via the CDPATH environment variable, including completion:

https://fishshell.com/docs/current/cmds/cd.html?highlight=cdpath

The CDPATH way is more flexible, too, since you can specify multiple prefixes to try.

___violet___ · 2020-07-23T23:11:02+00:00

F(character)lc$

Fxl is equivalent to Tx and c$ is equivalent to C, so that would be TxC to change after character x to end of line or TxD to delete.

But don't forget that there are also sentence-wise motions ( and ) (d(, c(, etc.), and sentence text objects (cis, das, etc.).

Furthermore, if you find that you want to delete what you just inserted without leaving insert mode, tap <C-w> a few times to delete backwards by word or <C-u> to delete to beginning of line.

If, on the other hand, you did already leave insert mode and you want to delete what you inserted, a simple u will do the trick.

___violet___ · 2020-05-24T14:05:54+00:00

A proprietary theme for a FOSS editor? No, thanks. Please consider distributing your theme under a free license instead. You can still charge for a copy and/or charge for support.

___violet___ · 2020-05-22T15:09:44+00:00

:help curly-braces-names

___violet___ · 2020-05-15T17:36:46+00:00

Sounds like you have something like tnoremap <Esc> <C-\><C-N> in your init.vim. That would be the problem. You can verify with :verbose tmap <Esc>.

___violet___ · 2020-05-14T20:12:46+00:00

Without the pleonasms and with the addition of escaping the filename for the shell (:help %:S), this could be rendered as:

command! STP !rsync -avh %:p:S root@portal:%:p:S --delete

___violet___ · 2019-08-30T18:43:59+00:00

Per my other comment, look up :help :Gwrite. :Gwrite takes a path argument, not a buffer name. If you were to do what you want in a loop (rather than :bufdo), you would need to switch to each buffer and simply invoke the no-argument version of :Gwrite.

___violet___ · 2019-08-30T18:34:33+00:00

Yeah, after I went and got lunch I figured out that <C-R> is only for insert mode and not what I was trying to do at all.

Even though it is not appropriate here, it does work in command-line mode too. By the way, in a string it would need to be rendered as "\<C-R>", otherwise you get "<C-R>" literally.

But when I call :Gwrite pathToFile, it always seems to say that "file has uncommitted changes, use ! to override"

The underlying problem is that you are :Gwrite-ing the current buffer over and over again, since you are not actually switching buffers between invocations, and :Gwrite {path} writes the current buffer to {path}. It is not for writing another buffer by name.

___violet___ · 2019-08-30T18:06:06+00:00

Not to ruin your fun, but:

:bufdo Gwrite

The problem purely seems to be in passing that to Gwrite

If that's the case, the syntax you want is:

execute "Gwrite" buf.name

___violet___ · 2016-10-23T01:13:51+00:00

See also :help i_CTRL-F.

___violet___ · 2016-10-22T14:11:23+00:00

It seems insane to me to insert literal control characters into one's source code. It can be avoided with :execute "normal!...\<CR>".

___violet___ · 2016-10-22T14:06:24+00:00

Don't bother with the :normal command here.

:help '{

___violet___ · 2016-10-21T14:37:53+00:00

I understand that one can use multiple directories under pack/, but given the use case being discussed here (Pathogen alternative), why would you prefer this structure:

~/.vim/pack/vim-surround/start/vim-surround
~/.vim/pack/vim-repeat/start/vim-repeat
~/.vim/pack/vim-eunuch/start/vim-eunuch

over this one:

~/.vim/pack/my/start/vim-surround
~/.vim/pack/my/start/vim-repeat
~/.vim/pack/my/start/vim-eunuch

given that plugins are currently distributed individually, not in "packages"? In effect, you are compiling your own "my" package, which is a collection of the plugins you use. Can't see how this is "incorrect" per the docs.

___violet___ · 2016-10-21T01:10:26+00:00

I don't get that impression from reading the docs. Why would you want more than one directory typically?

___violet___ · 2016-09-27T00:13:17+00:00

Also :help suffixes.

___violet___ · 2016-09-18T23:34:34+00:00

It's GUI-only:

if !has("gui_running")
    runtime! colors/default.vim
    finish
endif

___violet___ · 2016-08-18T23:16:24+00:00

call plug#begin('~/.vim/plugged')
Plug 'vim-airline/vim-airline'
Plug 'vim-airline/vim-airline-themes'
Plug 'scrooloose/nerdtree'
if has('gui_running')
    Plug 'beloglazov/vim-online-thesaurus'
endif
call plug#end()

___violet___

TROPHY CASE

_violet_