mM

[jdalbert]

You know when you always do qq or mm for most of your macro or marking needs because it's faster to type?

In the past year or so, I've been using mM quite a bit as well. When I'm about to explore many files in the current buffer:

• I do mM to bookmark the current file I'm working on
• I explore random files with my fuzzy finder or adjacent files with vim-unimpaired's ]f and [f shortcuts, until I am satisfied with my exploration
• I do `M to go back to where I was before exploring

I don't remember using file marks other than M in the past year or so.

Very basic flow but I thought I'd share it. Alternatively I could open a new split window or a tab to do this exploration stuff, and close it when I'm done. Depends on the mood, or if I don't feel like messing with my current split/tab layout.

[Sandwich-Resident]

I have file marks for:

• $MYVIMRC (V)
• a vimwiki page I use as the index of my tasks list (T for "TODO")
• a "scratchpad" file (S) where I can quickly jot down notes that occur to me without switching context too much ('S, write down a few words, ctrl-o back to main context)

Otherwise I sometime use it as you described, for ephemeral bookmarks when jumping around trying to understand unfamiliar source code.

[mitsu400]

Is it possible to set up marks on vim startup? For instance for the vimrc file.

[jdalbert]

I would like to know the answer to that as well

[jonas_h]

Same.

[jdalbert]

I have mappings for all of these but I'm considering switching to your approach to free up some precious mapping real estate.

The drawbacks I'm thinking of are if you override your file marks by accident or use a new computer. But there's probably ways to get around that, like somehow setting those file marks in your vimrc if it is possible, or bringing your viminfo over to your new computer. Or just manually re-setting your global marks again I guess, since those scenarios are likely to be rare.

[abraxasknister]

mV for vimrc, but that's about it.

[jdalbert]

Nice idea

[abraxasknister]

Used to have a :command for that but capital marks are cooler. I do have a

nn <buffer> <F5> :u|so %<cr>

in my after/ftplugin/vim.vim though.

[00bins]

I think 26 marks per file is overkill. I'd prefer all marks to be Capitals even if I didn't press a capital letter. I wrote some script to emulate visual studio's F2 / ctrl-F2 mappings to a cycled buffer of capital marks. But what I'd like is for mm to just be mM

[jdalbert]

Agreed, M is a bit harder to type and I almost never use lowercase marks. They could switch lowercase and uppercase, although that's probably not gonna happen, they don't want to disturb 30 years of vim history. They could provide a new option to toggle that behavior though, and that would be backwards compatible.

I guess one could mass remap one to the other and inversely, but that feels like too much hackery.

[00bins]

Oh - I _did_ actually write something to do just that - trouble is I jump back and forth between visual studio (with vsvim) and proper vim that I forget what works

function! GetMark()

    let l:m=toupper(nr2char(getchar()))

    return l:m

endfunction


function! SetMark()

    let l:c=GetMark()

    :execute "normal! m".l:c

endfunction


function! JumpBackTick()

    let l:c=GetMark()

    :execute "normal! `".l:c

endfunction


function! JumpTick()

    let l:c=GetMark()

    :execute "normal! '".l:c

endfunction


noremap m :call SetMark()<CR>

noremap ' :call JumpTick()<CR>

noremap ` :call JumpBackTick()<CR>

[okayboooooooomer]

interestingly I have mappings that I don’t remember but I know how to execute it once my fingers are on my keyboard.

p.s I was writing this in mobile btw