= On [2012-05-25 22:26:49 -0700]:
John Little Said:
On Saturday, May 26, 2012 1:47:05 PM UTC+12, miles christopher wrote:
I write a function like this ...
Your function works for me if I invoke it like this:
:call VimwikiWeblinkHandler(expand(cWORD))
I just press Enter on link directly.
Hi Adam,
I'm using VIM to develop my projects every day. They are mainly C code
with some perl/python/batch and makefiles. You didn't mention which OS
you are using. So i just want to share my experience on Windows.
cscope is a great plugin to do what you want even though it isn't
updated for a
On May 25, 2012, at 7:03 PM, sc wrote:
when you start with an empty window, you have done nothing to
tell vim what type of file you are going to create -- when you
add text it still doesn't know -- if you write the file with a
markdown extent, it COULD know if you would ask it to check
On May 25, 2012, at 9:41 PM, Chris Jones wrote:
There are things I find a little unclear regarding autocommands but
assuming the file extension is something like ‘*.mkdwn’ shouldn't it be
possible to achieve this automatically when creating the file by placing
something like this in a file
On May 25, 2012, at 10:12 PM, Chris Jones wrote:
On Fri, May 25, 2012 at 06:35:28PM EDT, Eric Weir wrote:
Thanks, Chris. It depends on the filetype. If it's markdown the result
is foldmethod=expr. Otherwise foldmethod=manual.
So it looks like the markdown script gets loaded when dealing
Hi,
I'd like to visualize specific space characters through the *conceal*
mechanism.
Here's my first (failed) attempt:
syntax match ThreePerEmSpace conceal cchar=⅓
syntax match FourPerEmSpace conceal cchar=¼
Greetings,
--
b.d
(| |)
^ ^
--
You received this message from the
On Saturday, May 26, 2012 6:48:00 PM UTC+12, miles christopher wrote:
I just press Enter on link directly.
Just pressing Enter in vim doesn't call functions; you must be using a plugin
that maps the Enter key, perhaps a filetype plugin that vim has loaded
automatically. I was trying to find
On Do, 24 Mai 2012, Christian Brabandt wrote:
On Do, 24 Mai 2012, Bob von Knobloch wrote:
Hi, I've searched all over but can't find an answer. How can one perform
commands like ':%s/\n/\r\r/g' (replacing newlines or tabs etc.) in the
gui's 'find and replace' dialogue?
Not possible, the
On Sat, May 26, 2012 at 05:54:32AM -0400, Eric Weir wrote:
On May 25, 2012, at 7:03 PM, sc wrote:
when you start with an empty window, you have done nothing to
tell vim what type of file you are going to create -- when you
add text it still doesn't know -- if you write the file with a
After splitting a window :sp there is now
an upper and lower window with a statusline between
them.
Is it possible to not have such a window-separating
statusline; the text from both windows would simply
be right next to each other without a separator?
Thanks
Richard
--
Quis custodiet ipsos
You are in console (non-gui) Vim and have split the
window (:sp). In the upper window you launch a script
that calls getchar().
What I'd like to be able to do is while the upper
window script is waiting on getchar(), switch to the
lower window and have a normal editing session and, then,
when I
On 2012-05-25, Chris Jones wrote:
There are things I find a little unclear regarding autocommands but
assuming the file extension is something like ‘*.mkdwn’ shouldn't it be
possible to achieve this automatically when creating the file by placing
something like this in a file named
I use Chip Campbell's Align plulgin:
http://vim.sourceforge.net/scripts/script.php?script_id=1195
Install the plugin, open your LaTeX file, visually-select the lines
of your table (V), and type \tt.
Thanks, Gary!
In addition, there's also AutoAlign which works with Align.vim...
On Sat, May 26, 2012 at 1:54 AM, Eric Weir eew...@bellsouth.net wrote:
Thanks, sc. Definitely does. I assumed the behavior was anomalous. Someone, I
think Chris, suggested earlier that a simple :e would do the trick, and it
seems to do so. [Is that a shortened version of the command you
On Sat, May 26, 2012 at 06:47:59AM EDT, Eric Weir wrote:
On May 25, 2012, at 10:12 PM, Chris Jones wrote:
[..]
I don't know when it became effective, but my understanding is that
markdown support is built into Vim.
I ran a quick test on a freshly-installed Vim 7.3 and highlighting
worked
On 2012-05-26, Gary Johnson wrote:
On 2012-05-25, Chris Jones wrote:
There are things I find a little unclear regarding autocommands but
assuming the file extension is something like ‘*.mkdwn’ shouldn't it be
possible to achieve this automatically when creating the file by placing
On May 26, 2012, at 6:32 PM, Chris Jones wrote:
On Sat, May 26, 2012 at 06:47:59AM EDT, Eric Weir wrote:
I don't know when it became effective, but my understanding is that
markdown support is built into Vim.
I ran a quick test on a freshly-installed Vim 7.3 and highlighting
worked
On May 26, 2012, at 11:44 AM, sc wrote:
On Sat, May 26, 2012 at 05:54:32AM -0400, Eric Weir wrote:
[Is that a shortened version of the command you suggest?]
no, :e is shorthand for :edit, which reloads the buffer and triggers
filetype detection along the way
the bad news is you've
On Sat, May 26, 2012 at 03:50:24PM EDT, Gary Johnson wrote:
On 2012-05-25, Chris Jones wrote:
There are things I find a little unclear regarding autocommands but
assuming the file extension is something like ‘*.mkdwn’ shouldn't it be
possible to achieve this automatically when creating
On Sat, May 26, 2012 at 08:38:28PM EDT, Eric Weir wrote:
On May 26, 2012, at 6:32 PM, Chris Jones wrote:
[..]
As soon as I issued a ‘:w /tmp/sample.mdown’ to write the [No Name]
buffer to disk , the markdown was highlighted.
Thanks, Chris. I did same with an .mkd extent and got the same
On 26/05/12 18:43, richard emberson wrote:
After splitting a window :sp there is now
an upper and lower window with a statusline between
them.
Is it possible to not have such a window-separating
statusline; the text from both windows would simply
be right next to each other without a separator?
21 matches
Mail list logo
