ly you can resurrect whatever portions of your original
web site that you'd like to keep.
Michael Henry
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist
to me. Thanks for the rapid response! You've
really been putting in the time lately. Bram left some big
shoes to fill, and I appreciate how hard you have been working
for the Vim community.
Michael Henry
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your
in general
take much longer to execute than the integer conversion code. I
think it's unlikely the difference could be measured in a Vim
benchmark. Since a helper function like this is general-purpose
code, I'd prefer the exact implementation unless profiling
demonstrates a performance bottl
```
In the sample program change `CHECK_ADDITION` to `0` to demonstrate the
need for the second check.
Michael Henry
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visi
4483f42b95adafb3f07b62479df7f808 M src
bisect run success
This technique helps when the commit message doesn't
necessarily mention the text you are searching for.
Michael Henry
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below th
ons:
- Is there a simpler way to solve this?
- Will the complex regular expression cause performance problems?
Any suggestions or comments are welcome.
Michael Henry
Here's the pull request containing the complex solution shown below:
https://github.com/marshallward/vim-restructuredtext/pull/63
The com
At present it appears that hard-coding knowledge of certain
terminals into Vim's source is the solution for determining the
correct mouse protocol, which is why I proposed adding support
for tmux in the above function. Is there a different way Vim
should be detecting the mouse protocol?
Michael
&& (term_is_xterm
|| STRNICMP(name, "screen", 6) == 0
+|| STRNICMP(name, "tmux", 4) == 0
|| STRICMP(name, "st") == 0
|| STRNICMP(name, "st-", 3) == 0
|| STRNICMP(name, "stterm", 6) == 0));
Tha
On 08/18/2016 02:11 PM, Yegappan Lakshmanan wrote:
> On Thu, Aug 18, 2016 at 5:48 AM, Michael Henry <v...@drmikehenry.com>
wrote:
>> I was trying to find something in the help regarding the meaning
>> of a "window id". Though there are several functions that
>
er values can always override the default. I'll
also note that I've seen 100ms used elsewhere, such as in Tim
Pope's "Sensible Defaults" plugin:
https://github.com/tpope/vim-sensible/blob/master/plugin/sensible.vim#L28
Michael Henry
--
--
You received this message from the "vim
On 08/17/2016 01:58 PM, Yegappan Lakshmanan wrote:
> On Wed, Aug 17, 2016 at 4:12 AM, Michael Henry <v...@drmikehenry.com>
wrote:
>> I'd like functions that:
>>
>> - Return True if a given window is a QuickFix or Location List
>> window.
>> [...]
>
&
lier hacks you see below.
I thought I'd seen some activity along these lines that might
expose the details directly, but I haven't been keeping up with
all of the new changes.
Michael Henry
Sample functions for reference
" Retu
the position of a
mark:
let save_a_mark = getpos('a)
...
- call setpos(''a', save_a_mark
+ call setpos('a, save_a_mark
Also see |getcurpos()| and |setpos()|.
Michael Henry
--
--
You
be a single line. If your paragraphs are currently separated with empty
Thanks,
Michael Henry
--
--
You received this message from the vim_dev 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
];
Michael Henry
--
--
You received this message from the vim_dev 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_dev group
, it will
be a well-deserved vacation :-)
Michael Henry
--
--
You received this message from the vim_dev 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
On 10/28/2013 07:41 AM, Bram Moolenaar wrote:
Michael Henry wrote:
So I suggest that a single global option that simply switches on
support for extended modifier for all keys, regardless whether
those keys are mapped, may well be good enough and might make
the implementation simple enough
be convinced to
support this feature, users like myself will still have the
benefits (which are substantial, IMO).
Michael Henry
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http
:-)
Michael Henry
--
--
You received this message from the vim_dev 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_dev group
timers
that are operating properly?
Michael Henry
--
--
You received this message from the vim_dev 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
, but generally a FocusLost event
should not do something like this, because it can happen at any time.
Reading the tip on the wiki, it's recommending :wa, not
:write, which is similar to Bram's suggested :update in that
it writes only modified files.
Michael Henry
--
--
You received this message from
(/\./, '')[0,2]`
if test X$rubyversion = X; then
rubyversion=`$vi_cv_path_ruby -e print ((VERSION rescue
RUBY_VERSION)).gsub(/\./, '')[0,2]`
fi
Yes, this works fine for me. It seems like a good work-around
to me.
Thanks,
Michael Henry
--
--
You received this message from the vim_dev
,
Michael Henry
--
--
You received this message from the vim_dev 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_dev group
reopen the Fedora ticket.
Thanks for any help,
Michael Henry
--
--
You received this message from the vim_dev 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
On 02/23/2013 07:16 PM, John Little wrote:
On Sunday, February 24, 2013 2:15:47 AM UTC+13, Michael Henry wrote:
Each time the spacebar is pressed, the value of 'columns' will be
displayed at four points in time.
My vim 7.3.820 on Kubuntu misbehaves much more than yours.
All I have to do
isolated it to a somewhat repeatable
test).
Thanks,
Michael Henry
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Feb 23 2013 07:51:24)
Included patches: 1-831
Compiled by v...@drmikehenry.com
Huge version with GTK2 GUI. Features included (+) or not (-):
+arabic -ebcdic +listcmds
after
backward searches. The only work-around my brain can handle is
to simply avoid backward searches entirely; instead, I search
forward and press N.
Michael Henry
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
of scrolling the window. The price I pay for
this is the need to press ``n`` (or ``N``) immediately if I want
to find the next (or previous) match. I find this a good
trade-off, but your mileage may vary.
Michael Henry
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type
On 02/17/2013 12:11 PM, Bram Moolenaar wrote:
On 02/15/2013 05:57 PM, Michael Henry wrote:
If there is anything you'd like me to adjust about either patch
to make the change suitable for inclusion, please let me know.
Thanks for the patch. Bug fixes go first, thus it's somewhere down
. The modified patch below
removed the idea of a new Vim option.
If there is anything you'd like me to adjust about either patch
to make the change suitable for inclusion, please let me know.
Thanks,
Michael Henry
On 01/30/2013 09:14 AM, Michael Henry wrote:
On 01/29/2013 04:33 PM, Bram Moolenaar
be in favor of making the behavior non-optional. Here is a
modification to the patch that removes the option.
Michael Henry
diff -r 274c841f033a runtime/doc/map.txt
--- a/runtime/doc/map.txtFri Jan 25 20:11:01 2013 +0100
+++ b/runtime/doc/map.txtWed Jan 30 09:13:18 2013 -0500
@@ -654,6
with the minor code
change. I didn't know how to implement a test for this
functionality. If anyone has a suggestion on that front, I'd be
happy to try to implement something.
Michael Henry
diff -r 274c841f033a runtime/doc/map.txt
--- a/runtime/doc/map.txtFri Jan 25 20:11:01 2013 +0100
+++ b/runtime/doc
the following error message:
Error detected while processing command line:
E48: Not allowed in sandbox: sandbox setlocal ts=16
I was expecting :setlocal would work with :sandbox; should it?
Thanks,
Michael Henry
--
You received this message from the vim_dev maillist.
Do not top-post! Type your
is still there for the LustyExplorer plugin. I suspect
that's a problem with the plugin and ruby 1.9, but I'll look
into that separately and submit a bug report to the plugin
author.
Thanks for the prompt patches :-)
Michael Henry
--
You received this message from the vim_dev maillist.
For more
On 12/02/2009 11:59 AM, Bram Moolenaar wrote:
Patch 7.2.315
Problem:Python libs can't be found on 64 bit system.
Solution: Add lib64 to the list of directories. (Michael Henry)
Files:src/auto/configure, src/configure.in
Thanks, Bram, I can confirm that this patch works
seem very friendly to me.
Michael Henry
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
the following document
interesting and helpful for posting questions on mailing lists:
http://www.catb.org/~esr/faqs/smart-questions.html
Hope this helps,
Michael Henry
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information
silent when
your question shows up. But there are a number of helpful experts on
this mailing list, so if you make your code available in a relatively
easy to access manner (no login required, etc.) and someone recognizes
what's going on, they will probably try to help you.
Hope this helps,
Michael
Bram Moolenaar wrote:
Michael Henry wrote:
It appears that the output from :echo and :echomsg does not
show up properly when used from the Command-line window
while a QuickFix window is open.
[...]
If you use:
:echo hello\nthere
You get the hit-enter prompt before
by
disabling the use of xargs entirely (via the Grep_Find_Use_Xargs
variable) but this comes at a performance penalty.
Thanks,
Michael Henry
[1]: http://www.vim.org/scripts/script.php?script_id=311
[2]: http://www.tomshardware.com/ucg/commands/xargs-15408.html
[3]: http://www.opengroup.org/onlinepubs
in the example given above.
The attached patch fixes this problem by using the MoveWindowStructure()
function[4], whose coordinates are compatible with those used for the
GetWindowBounds() function.
Michael Henry
[1]: For the curious non-mac user: The bug may be simulated on a
correctly operating gvim
41 matches
Mail list logo
