On Wednesday, March 9, 2016 at 2:43:18 AM UTC+1, h_east wrote:
> Hello Thomas!
>
> 2016-3-8(Tue) 19:04:06 UTC+9 Thomas R.:
> > Hello,
> >
> > I'm trying to remap the shortcut so it goes to the definition but
> > using a new tab. For example using .
> >
> > I have tried the following in my vimr
as the title said
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_u
add the following to your vimrc:
let myfile='/path/to/your/file'
then you can invoke vim with
vim -c 'exe "e ".myfile'
which is a bit awkward, so you might want to make an alias if you
intend to do it frequently.
-tim
--
--
You received this message from the "vim_use" maillist.
Do no
2016-03-09 17:02 GMT+03:00 Tim Chase :
> add the following to your vimrc:
>
>let myfile='/path/to/your/file'
>
> then you can invoke vim with
>
>vim -c 'exe "e ".myfile'
>
> which is a bit awkward, so you might want to make an alias if you
> intend to do it frequently.
You forgot `fnameesc
Den 2016-03-09 kl. 15:33, skrev Nikolay Aleksandrovich Pavlov:
Unlike your variant which does not allow a huge number of characters
including spaces and `[]` which are not uncommon,
Square brackets in filenames is common?
Where did "ASCII alphanumerics, hyphen, underscore and period" go?
I do o
I have a file `a.txt`.
When I use root to edit this file `sudo vi a.txt`. Vim prompt:
`E474: Invalid argument:
listchars=eol:¬,tab:>·,trail:~,extends:>,precedes:<,space:␣`
But when I user `vi a.txt` without `sudo`. All things right.
I have tried this:
http://stackoverflow.com/questions/1832153
2016-03-09 23:54 GMT+03:00 BPJ :
> Den 2016-03-09 kl. 15:33, skrev Nikolay Aleksandrovich Pavlov:
>>
>> Unlike your variant which does not allow a huge number of characters
>> including spaces and `[]` which are not uncommon,
>
>
> Square brackets in filenames is common?
Every second *.ass/*.srt/…
* 童虎 [2016-03-10 00:54]:
> I have a file `a.txt`.
> When I use root to edit this file `sudo vi a.txt`. Vim prompt:
>
> `E474: Invalid argument:
> listchars=eol:¬,tab:>·,trail:~,extends:>,precedes:<,space:␣`
>
> But when I user `vi a.txt` without `sudo`. All things right.
May be Vim that runs
On 2016-03-09 01:34, 童虎 wrote:
> I have a file `a.txt`.
> When I use root to edit this file `sudo vi a.txt`. Vim prompt:
First, I'd use "sudoedit" which invokes $SUDO_EDITOR environment
variable, falling back to $VISUAL, and then $EDITOR if needed.
Since it runs vim as you rather than as root, t
On Wed, Mar 09, 2016 at 01:34:46AM -0800, 童虎 wrote:
> I have a file `a.txt`.
> When I use root to edit this file `sudo vi a.txt`. Vim prompt:
>
> `E474: Invalid argument:
> listchars=eol:¬,tab:>·,trail:~,extends:>,precedes:<,space:␣`
>
> But when I user `vi a.txt` without `sudo`. All things ri
Say I have a directory with two files junk1.txt, junk2.txt. In zsh, if I do
vim 1
it expands to
vim junk1.txt
Is it possible to have this kind of completion when opening files in
gvim as well? For example, commands such as
:e 1
:find 1
:tabf 1
should expand to
:e junk1.txt
:find junk1.txt
:tab
11 matches
Mail list logo
