Why VIM backup filenames are not correct? 'backupdir' option not performing as expected -



Why VIM backup filenames are not correct? 'backupdir' option not performing as expected -

i'm building custom vimrc improve workflow, , liked thought of setting centralized directory maintain backup, swap , undo files together, this:

" === backup settings === " turn backup on set backup set backupdir=~/.vim/backup// " === swap files === " turn swap files on set swapfile set directory=~/.vim/swap// " === undo files === " turn undofiles on set undofile set undodir=~/.vim/undo//

the double trailing slash supposed result in filename expansion, resulting backup/swap/undo filename total path, % replacing every /, %home%username%path%to%your%file.ext.

everything works swap , undo files, backups refuses work, generating filenames in format file.ext~ without total path expansion, means when edit 2 files same name, backup of first lost (overwritten second).

does have clue problem?

it seems 'backupdir' alternative doesn't back upwards translation of total absolute path filename (using % path separators) 'directory' , 'undodir' do. @ to the lowest degree nil mentioned under :help 'backupdir'.

since inconsistent, , see utilize case, should submit request @ vim_dev mailing list. actually, there such patch in (veeery long) patch queue (:help todo.txt):

7 'directory' alternative supports changing path separators "%" create file names unique, back upwards 'backupdir'. (mikolaj machowski) patch christian brabandt, 2010 oct 21.

please kindly lobby on vim_dev mailing list have priority raised!

vim

Comments

Post a Comment

Popular posts from this blog

assembly - What is the addressing mode for ld, add, and rjmp instructions? -

assembly - What is the addressing mode for ld, add, and rjmp instructions? - hey guys know ldi (load immediate) addressing mode set immediate , st instruction addressing mode set index. however, have no thought others curious are! thanks :) the addressing modes explained in instruction set, in first few pages. in table of instructions see operands instruction determine addressing mode. mode indicated arguments assembly instruction. for example, ld had several different ways of operating, depending on arguments. 1 of them ld rd,x d number of register, such ld r3,x . ld r3,-z else (although both indirect addressing). rjmp k relative addressing, jumping pc + k + 1. add rr,rd direct register addressing. result contained in rd. assembly avr instructions
Read more

vowpalwabbit - Interpreting Vowpal Wabbit results: Why are some lines appended by "h"? -

vowpalwabbit - Interpreting Vowpal Wabbit results: Why are some lines appended by "h"? - below part of log training vw model. why of these lines followed h? you'll notice that's true of "average loss" line in summary @ end. i'm not sure means, or if should care. ... average since illustration illustration current current current loss lastly counter weight label predict features 1.000000 1.000000 1 1.0 -1.0000 0.0000 15 0.500000 0.000000 2 2.0 1.0000 1.0000 15 1.250000 2.000000 4 4.0 -1.0000 1.0000 9 1.167489 1.084979 8 8.0 -1.0000 1.0000 29 1.291439 1.415389 16 16.0 1.0000 1.0000 45 1.096302 0.901166 32 32.0 -1.0000 -1.0000 21 1.299807 1.503312 64 64.0 -1.0000 1.0000 ...
Read more

Is there a way to convert an HTML page styled with Bootstrap CSS into email-compatible html? -

Is there a way to convert an HTML page styled with Bootstrap CSS into email-compatible html? - is there way convert html page styled bootstrap css html email compatible form? see there exclusively different css frameworks, ink, creating email compatible html, there flow creating email doesn't require utilize of different css framework? there html -> pdf -> email html flow? or other flow? no, couple of reasons... first, there no reliable css or html email. clients on place in terms of css back upwards & how render html, structural/semantic problem. isn't converting classes much altering html structure. as explained in this css tricks post, typical solution ol-skool techniques table-based layouts, requiring exclusively restructure existing html. have add together client-specific hacks. second, , more importantly, shouldn't send everything on existing page email. if it's newsletter subscribers, people won't read it. instead, create ...
Read more