On 1/08/12 1:05 PM, ping wrote:
b.t.w, just curious is there anything about vim that you don't know of? :D
Yeah, but I try not to answer those questions.
Smiles,
Ben.
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/31/2012 10:38 PM, sc wrote:
> On Tue, Jul 31, 2012 at 01:20:14PM -0700, jeroen wrote:
>> On Tuesday, July 31, 2012 9:41:09 PM UTC+2, Ben Fritz wrote:
>>>
>>> Then I will usually use f, F, t, or T, or a / search, or
>>> w/W/b/B to get to the co
hi all,
i gather from the lack of response that my previous question has no
feasible answer. anyway, i have updated the question a bit to give some
other possible ways of solving the problem. any pointers in the right
direction would be much appreciated. i am pretty competent with vim but i
have l
On 7/31/2012 10:52 PM, Ben Schmidt wrote:
thanks, but...
I tried following, still I need to press 4 enter...
function! s:Asciidoc2All()
let a:destdir = "/Dropbox/temp-transfer/"
let a:filebasename = "%:t:r"
let tohtml = "silent w|!asciidoc -a toc -a toclevels=6 -o" . a:destdir
. "/" .
a:filebase
thanks, but...
I tried following, still I need to press 4 enter...
function! s:Asciidoc2All()
let a:destdir = "/Dropbox/temp-transfer/"
let a:filebasename = "%:t:r"
let tohtml = "silent w|!asciidoc -a toc -a toclevels=6 -o" . a:destdir . "/" .
a:filebasename . ".html \"%\""
let tofodt = "silent w
Yes, my vim correctly detected Verilog file.
I use ctags 5.8.
-邮件原件-
发件人: vim_use@googlegroups.com [mailto:vim_use@googlegroups.com] 代表
David Fishburn
发送时间: 2012年8月1日 2:56
收件人: vim_use@googlegroups.com
抄送: vim_use@googlegroups.com
主题: Re: Ctags or taglsit can support verilog?
On Jul 31,
On 7/31/2012 8:13 PM, Ben Schmidt wrote:
On 1/08/12 10:07 AM, Ben Schmidt wrote:
filetype=asciidoc
Last set from /etc/vim/ftdetect/asciidoc_filetype.vim
what is that /etc/vim/ folder doing here?
runtimepath=~/.vim,/usr/share/vim/vimfiles,/usr/share/vim/vim73,/usr/share/vim/vimfiles/after,~/.vi
On 7/31/2012 8:17 PM, Ben Schmidt wrote:
On 1/08/12 7:38 AM, ping wrote:
hi experts:
I now everything after
:!ext-prog
will be treated as param of that ext-prog. so I can't
:!ext-prog param1 param2
but then how to avoid keep typing in following cases?
command! AsciidocA call s:Asciidoc2All()
Yves S. Garret wrote:
> How do I turn of _all_ auto-indentation and just
> have me worry about that stuff?
See:
http://vim.wikia.com/wiki/How_to_stop_auto_indenting
> What am I doing wrong and what is the purpose of :close?
The :close command closes the current window, whereas you want
to "close
The help page on key-notation (:help key-notation) states that several keys are
equivalent for others
- and
- and
- and
For most keys this appears to be true. Attempts to map with the LHS of
and would conflict and the last one typed would win. For example
:imap hit tab
:imap hit co
On Tue, Jul 31, 2012 at 04:33:47PM -0400, Yves S. Garret wrote:
> Hello,
> 2 - Say I'm modifying multiple files. The "buffers" feature makes it much
> easier to have multiple files in a single window and then switch between
> them. This keeps my desktop sane by having just one window to look at.
On 1/08/12 7:38 AM, ping wrote:
hi experts:
I now everything after
:!ext-prog
will be treated as param of that ext-prog. so I can't
:!ext-prog param1 param2
but then how to avoid keep typing in following cases?
command! AsciidocA call s:Asciidoc2All()
function! s:Asciidoc2All()
w|!asciidoc -a
On 1/08/12 10:07 AM, Ben Schmidt wrote:
filetype=asciidoc
Last set from /etc/vim/ftdetect/asciidoc_filetype.vim
what is that /etc/vim/ folder doing here?
runtimepath=~/.vim,/usr/share/vim/vimfiles,/usr/share/vim/vim73,/usr/share/vim/vimfiles/after,~/.vim/after
:scriptnames
1: /usr/share/vim
On Tue, Jul 31, 2012 at 02:58:55PM EDT, Daan wrote:
> I've been learning Vim for a while, and one situation has been coming
> up a lot for me:
>
> 1) I'm scrolling through a sourcefile, and see an interesting word I'd
> like to edit or yank. 2) I look left at the line number of the word,
> and ty
filetype=asciidoc
Last set from /etc/vim/ftdetect/asciidoc_filetype.vim
what is that /etc/vim/ folder doing here?
runtimepath=~/.vim,/usr/share/vim/vimfiles,/usr/share/vim/vim73,/usr/share/vim/vimfiles/after,~/.vim/after
:scriptnames
1: /usr/share/vim/vimrc
2: /usr/share/vim/vim73/syntax/synt
On 2012-07-31, Yves S. Garret wrote:
> Hello,
>
>I've started to use gVim in place of Notepad++ on my Windows 7 machine
> (something I prefer since I use vim on my Ubuntu box). However, I'm running
> into 2 particular issues that are quite annoying.
>
> 1 - When I try to modify JavaScript an
hi experts:
I now everything after
:!ext-prog
will be treated as param of that ext-prog. so I can't
:!ext-prog param1 param2
but then how to avoid keep typing in following cases?
command! AsciidocA call s:Asciidoc2All()
function! s:Asciidoc2All()
w|!asciidoc -a toc -a toclevels=6 -o
/mnt/
Hello,
I've started to use gVim in place of Notepad++ on my Windows 7 machine
(something I prefer since I use vim on my Ubuntu box). However, I'm
running into 2 particular issues that are quite annoying.
1 - When I try to modify JavaScript and I write the function, the editor
automatically in
On Jul 31, 2012, at 3:38 PM, sc wrote:
> On Tue, Jul 31, 2012 at 01:20:14PM -0700, jeroen wrote:
>> On Tuesday, July 31, 2012 9:41:09 PM UTC+2, Ben Fritz wrote:
>>>
>>> Then I will usually use f, F, t, or T, or a / search, or w/W/b/B to get to
>>> the correct column, possibly with an initial
On Tue, Jul 31, 2012 at 01:20:14PM -0700, jeroen wrote:
> On Tuesday, July 31, 2012 9:41:09 PM UTC+2, Ben Fritz wrote:
> >
> > Then I will usually use f, F, t, or T, or a / search, or w/W/b/B to get to
> > the correct column, possibly with an initial _ or g_ to position the cursor
> > at the be
On Tuesday, July 31, 2012 9:41:09 PM UTC+2, Ben Fritz wrote:
>
> Then I will usually use f, F, t, or T, or a / search, or w/W/b/B to get to
> the correct column, possibly with an initial _ or g_ to position the cursor
> at the beginning or end of the line (or ^ and $, but I use Dvorak making _
On Tuesday, July 31, 2012 1:58:55 PM UTC-5, Daan wrote:
> I've been learning Vim for a while, and one situation has been coming up a
> lot for me:
>
> 1) I'm scrolling through a sourcefile, and see an interesting word I'd like
> to edit or yank.
> 2) I look left at the line number of the word, a
I've been learning Vim for a while, and one situation has been coming up a lot
for me:
1) I'm scrolling through a sourcefile, and see an interesting word I'd like to
edit or yank.
2) I look left at the line number of the word, and type [line number]G
3) I keep pressing w/W/b/B until I reach the
On Tuesday, July 31, 2012 12:09:25 PM UTC-5, rockybalboa4 wrote:
> What ways are there to check the buffer size?
>
>
>
> getfsize()
>
>
>
>
>
> redir @"
>
> execute "silent normal! g\"
>
> redir END
>
>
>
>
There's the line2byte() function as well. I assume you want size in byte
On Jul 31, 2012, at 6:16 AM, Leszek Świrski wrote:
> In case anyone else has the same problem, I fixed it by fixing my gvim path in
> HKLM\SOFTWARE\Vim\Gvim
> (It was set to vim72, I had vim73)
>
Which installer did you run to install Vim 7.3?
--
David Fishburn
--
You received this message
On Jul 31, 2012, at 12:59 PM, Ben Fritz wrote:
> On Monday, July 30, 2012 10:11:05 PM UTC-5, jun wang wrote:
>> I use ctags generate tags in Verilog file,but I enter “:TlistToggle”,it
>> display none
>> If I c file,it can work!
>> What happened?
>>
>> Best
>> Regard
>
> Is your Verilog file
What ways are there to check the buffer size?
getfsize()
redir @"
execute "silent normal! g\"
redir END
More?
--
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.or
On Monday, July 30, 2012 10:11:05 PM UTC-5, jun wang wrote:
> I use ctags generate tags in Verilog file,but I enter “:TlistToggle”,it
> display none
> If I c file,it can work!
> What happened?
>
> Best
> Regard
Is your Verilog file being correctly detected by Vim as a Verilog file type? If
me
On 2012-07-31, ping wrote:
> On 07/31/2012 11:08 AM, Gary Johnson wrote:
> >On 2012-07-31, ping wrote:
> >
> >>I tried these debugging tools but still have no clear clue.
> >>I even tried vim -V temp1.log or vim -V4 temp1.log, the 1st part of
> >>the result flushed away from my screen and I couldn'
On 07/31/2012 11:08 AM, Gary Johnson wrote:
On 2012-07-31, ping wrote:
I tried these debugging tools but still have no clear clue.
I even tried vim -V temp1.log or vim -V4 temp1.log, the 1st part of
the result flushed away from my screen and I couldn't capture
anything into here, from the res
On 2012-07-31, ping wrote:
> I tried these debugging tools but still have no clear clue.
> I even tried vim -V temp1.log or vim -V4 temp1.log, the 1st part of
> the result flushed away from my screen and I couldn't capture
> anything into here, from the rest of the output I couldn't find
> anythin
On Tue, 31 Jul 2012, Dotan Cohen wrote:
On Tue, Jul 31, 2012 at 3:24 PM, Benjamin R. Haskell wrote:
" h toggles the under-cursor highlighting
:map h let g:under_cursor_hl = 1 - get(g:, 'under_cursor_hl', 1)
" Use it in the CursorMoved autocmd
:autocmd CursorMoved * if get(g:, 'under_cursor_hl
I occasionally dabble with assembly code and one of the things which can
take more time than writing the instructions is keeping your in-line
comments (or following line continuation) correctly formatted so that they
don't wrap. My preference would be to keep assembly instructions on the
left and a
On Tue, Jul 31, 2012 at 3:24 PM, Benjamin R. Haskell wrote:
> " h toggles the under-cursor highlighting
> :map h let g:under_cursor_hl = 1 - get(g:, 'under_cursor_hl', 1)
>
> " Use it in the CursorMoved autocmd
> :autocmd CursorMoved * if get(g:, 'under_cursor_hl', 1) | exe printf('match
> IncSear
On Tue, Jul 31, 2012 at 3:23 PM, wrote:
> On Tuesday, 31 July 2012 12:51:52 UTC+1, dotancohen wrote:
> Here's another way to highlight the word under the cursor
>
> http://vim.wikia.com/wiki/VimTip1572
>
> If you use this plugin, you can simply enable the functionality
>
> \m
>
> then use a NumP
On Tue, 31 Jul 2012, Dotan Cohen wrote:
On Superuser I found this nice way to highlight the word under the
cursor for the whole page:
:autocmd CursorMoved * exe printf('match IncSearch /\V\<%s\>/',
escape(expand(''), '/\'))
http://superuser.com/questions/255024/vim-highlighting-a-search-term-
On Tuesday, 31 July 2012 12:51:52 UTC+1, dotancohen wrote:
> On Superuser I found this nice way to highlight the word under the
> cursor for the whole page:
> http://superuser.com/questions/255024/vim-highlighting-a-search-term-without-moving-the-cursor
>
> I would like to enable / disable this
On Superuser I found this nice way to highlight the word under the
cursor for the whole page:
:autocmd CursorMoved * exe printf('match IncSearch /\V\<%s\>/',
escape(expand(''), '/\'))
http://superuser.com/questions/255024/vim-highlighting-a-search-term-without-moving-the-cursor
I would like to en
In case anyone else has the same problem, I fixed it by fixing my gvim path in
HKLM\SOFTWARE\Vim\Gvim
(It was set to vim72, I had vim73)
--
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:
On 31/07/12 06:44, Dominique Pellé wrote:
Lucas Sanner wrote:
:language
"LC_COLLATE=French_France.1252;LC_TYPE=C;LC_MONETARY=French_France.
1252;LC_NUMERIC=C;LC_TIME=French_France.1252"
The 1252 there indicates that your locale is not using
Unicode but it's using the Windows code page 1252:
On 31/07/12 03:03, ping wrote:
On 7/30/2012 5:45 PM, Tim Chase wrote:
On 07/30/12 16:38, ping wrote:
guys:
I just run into an annoying issue.
I open a text file and found it was set to some filetype (say,
asciidoc).
this is not what I expected.
how to find out which config lines in which config
> By the way, you never indicated what version of Vim you're using.
I used the 7.3 GVim version
The subject topic you mentioned is relevant for my case
http://superuser.com/questions/207264/gvim-utf-8-in-windows
I installed the 2 dlls as described in the topic and it does
work now. Accentued ch
42 matches
Mail list logo
