On Thu, April 12, 2012 08:30, Christian Brabandt wrote:
> On Thu, April 12, 2012 08:13, Boyko Bantchev wrote:
>> The Euro sign is not the only difference between rfc1345 and the
>> output of :digraphs. I cannot tell what all of them are, but, e.g.,
>> the already mentioned /\ is known to Vim but i
On Thu, April 12, 2012 08:13, Boyko Bantchev wrote:
>> That is not true. Since 7.3.116 digraph.txt contains all digraphs
>> available.
>
> Nice to know that, but it seems a very recent addition.
If I recall correctly, it's more than a year ago, that I provided the
patch:
http://groups.google.com/g
> That is not true. Since 7.3.116 digraph.txt contains all digraphs available.
Nice to know that, but it seems a very recent addition.
I happen to be using several versions of Vim, the most recent being 7.3.46,
and none of them has all the chars in digraph.txt.
So, perhaps we should say, `That *is
Phil Dobbin a écrit:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/04/2012 22:01, Andre Majorel wrote:
>
> > On 2012-04-10 18:37 +0100, Phil Dobbin wrote:
> >
> >> Putting the documents (manual & reference) into tex I think is
> >> the best way to go & will result in a much be
The ':help :new' text includes:
This behaves like a ":split" first, and then a ":e" command.
Should that read:
This behaves like a ":split" first, and then an ":enew" command.
John
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text
On Wed, Apr 11, 2012 at 04:00:27PM EDT, Christian Brabandt wrote:
[..]
> That is not true. Since 7.3.116 digraph.txt contains all digraphs
> available.
Is there a format of the ‘:digraphs’ command that lets you list only
custom user-defined digraphs - i.e. those that are different from the
defa
On Wed, Apr 11, 2012 at 04:00:27PM EDT, Christian Brabandt wrote:
> Hi Boyko!
>
> On Mi, 11 Apr 2012, Boyko Bantchev wrote:
[..]
> > digraph.txt or, more specifically, :help digraph-table only show part
> > of the available digraphs (less than a half, I think).
[..]
> That is not true. Since 7
On Wed, Apr 11, 2012 at 02:26:03PM EDT, Boyko Bantchev wrote:
> > I have a hard time to find the symbol that I need in :diagraph. Is
> > there a table that better organize the symbols? In particular, I want
> > to type in $\times$. Could anybody let me know what is the shortcut?
>
> rfc1345 is wo
Hi Boyko!
On Mi, 11 Apr 2012, Boyko Bantchev wrote:
> > I have a hard time to find the symbol that I need in :diagraph. Is
> > there a table that better organize the symbols? In particular, I want
> > to type in $\times$. Could anybody let me know what is the shortcut?
>
> rfc1345 is worth check
On 11 Apr 2012, at 13:34, Francis (Grizzly) Smit wrote:
> On 11/04/12 20:46, John Beckett wrote:
>> Niels Kobschätzki wrote:
>>> I was wondering what the reasoning behind the existence of c,
>>> r and a is.
Thanks for pointing out the differences in the commands :)
Niels
--
You received this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/04/2012 22:01, Andre Majorel wrote:
> On 2012-04-10 18:37 +0100, Phil Dobbin wrote:
>
>> Putting the documents (manual & reference) into tex I think is
>> the best way to go & will result in a much better looking final
>> PDF from which to pr
> I have a hard time to find the symbol that I need in :diagraph. Is
> there a table that better organize the symbols? In particular, I want
> to type in $\times$. Could anybody let me know what is the shortcut?
rfc1345 is worth checking at times, but its digraph set is different
from Vim's, and t
Timothy Madden, Wed 2012-04-11 @ 20:44:44+0300:
> Is it possible to reformat code upon opening the file (or after a
> key-press), and show the buffer as "saved" (without writing the
> formatted code back) ?
You can clear the modified flag with `:set nomodified`.
I would use BufReadPost and BufWri
Hello!
I can reproduce. There seems to be an omission in the fortran.vim
ftplugin file, which for some reason doesn't include parentheses in
the b:match_words variable. You can get around the issue by appending
the text, ',(:)' to b:match_words, like the following: :let
b:match_words.=',(:)' Thi
Hello
My company has a new coding convention (coding style guidelines) that I
really do not like (it includes a tabsize of 4) and I would like to format
the text a little automatically on buffer load, and change it back on save,
but I do not want every source file I open with vim to show up as
"mo
On Wednesday, April 11, 2012 11:02:27 AM UTC-5, Thomas Mitterfellner wrote:
> Hello!
>
> I'm using the matchit plugin to match Fortran code structures with %,
> and it works as expected. But now it seems that normal parens are not
> matched with % anymore.
>
> In this code:
>
> do i = 1, 1000
Thomas Mitterfellner, Wed 2012-04-11 @ 18:02:27+0200:
> 1) Can you reproduce this behavior or is something wrong with my
> configuration?
I can't reproduce it. I just pasted your literal code snippet into a
Fortran buffer and was able to jump back and forth between the
parentheses with %.
I assum
Hello!
I'm using the matchit plugin to match Fortran code structures with %,
and it works as expected. But now it seems that normal parens are not
matched with % anymore.
In this code:
do i = 1, 1000
dep(i, 1) = 0.
end do
when pressing % with the cursor on the ( on a freshly opened file,
On 04/11/12 10:13, Yichao Zhou wrote:
Under some complex syntax, the speed of vim will become
somehow a little slow. The screen and text will blink when we
do the editing and moving. So can we let vim use double
buffer to avoid this problem?
It sounds like you might want to look into the 'laz
hi Tim:
thanks for the detailed explanation and great info.
but if you look at this:
http://vim.wikia.com/wiki/VimTip1063
you will know what exactly I wanted to achieve.
basically I want to define a "generic" keybind or customer command,
to capture the matches by last :[range]g command, and do so
Hello, everyone
Under some complex syntax, the speed of vim will become somehow a
little slow. The screen and text will blink when we do the editing
and moving. So can we let vim use double buffer to avoid this
problem?
Regards,
Yichao Zhou.
--
You received this message from the "vim_use" ma
A Loumiotis wrote:
Updating to v146c of netrw did not solve the problem.
Try v146d -- its difficult to do this without having a system to test
with, I'm sorry. I probably won't be able to get to trying to compile
and run a native windows vim again until this weekend
IMHO the problem lies w
On 04/10/12 22:19, Zarko Coklin wrote:
I am still not clear whether I should admire people who know
these things like some divine entities or judge them for not
having the life :-)
It's just like playing with Legos...you have various parts that
fit together in well-defined ways, and you just p
On Wed, Apr 11, 2012 at 11:29 AM, Marcin Szamotulski wrote:
> On 17:22 Tue 10 Apr , Charles Campbell wrote:
>> Marcin Szamotulski wrote:
>> > On 16:49 Tue 10 Apr , Charles Campbell wrote:
>> >
>> >> A Loumiotis wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> I'm facing exactly the same problem that
On 2012-04-10 16:54 -0400, shawn wilson wrote:
> On Tue, Apr 10, 2012 at 16:30, Andre Majorel wrote:
>
> > http://www.teaser.fr/~amajorel/vimpspp/
>
> is that what was used to create this: http://vimdoc.sourceforge.net/
No. Those are typeset in Courier.
--
André Majorel http://www.teaser.fr/~
the idea you are thinking about is similar as Python
Best Regards.
Wuhan,China.
2012/4/11 Niels Kobschätzki
> Hi,
>
> I was wondering what the reasoning behind the existence of c, r and a is.
> They are all the same but
> c works with move-commands (like cw)
> s works with prefixed numbers (li
On 11/04/12 20:46, John Beckett wrote:
Niels Kobschätzki wrote:
I was wondering what the reasoning behind the existence of c,
r and a is.
They are all the same but
c works with move-commands (like cw)
s works with prefixed numbers (like 4s)
r doesn't work with anything.
Why where three commands
Niels Kobschätzki wrote:
> I was wondering what the reasoning behind the existence of c,
> r and a is.
> They are all the same but
> c works with move-commands (like cw)
> s works with prefixed numbers (like 4s)
> r doesn't work with anything.
>
> Why where three commands for essentially the same t
Hi,
I was wondering what the reasoning behind the existence of c, r and a is.
They are all the same but
c works with move-commands (like cw)
s works with prefixed numbers (like 4s)
r doesn't work with anything.
Why where three commands for essentially the same thing once introduced? Why
not do
On 17:22 Tue 10 Apr , Charles Campbell wrote:
> Marcin Szamotulski wrote:
> > On 16:49 Tue 10 Apr , Charles Campbell wrote:
> >
> >> A Loumiotis wrote:
> >>
> >>> Hi,
> >>>
> >>> I'm facing exactly the same problem that Bart mentioned with netrw
> >>> v146a as well. I'm using gVi
30 matches
Mail list logo
