Thanks for the follow up.
--
Sent from a rotary phone rented from Ma Bell
--
--
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 messag
On Thursday, June 14, 2018 at 11:50:17 AM UTC-7, Tony Mechelynck wrote:
> So Vim seems to choke on the line
>
> let blacklist =
> \ get(g:, 'pathogen_blacklist', get(g:, 'pathogen_disabled', [])) +
> \ pathogen#split($VIMBLACKLIST)
>
> Maybe $VIMBLACKLIST is undefined? Or
On Thursday, June 14, 2018 at 11:34:48 AM UTC-7, Christian Brabandt wrote:
> On Do, 14 Jun 2018, Frew Schmidt wrote:
>
> > I use pathogen as my plugin manager and updated vim yesterday
>
> You know, that you don't need pathogen anymore since Vim 8?
I am aware, but the v
On Thursday, June 14, 2018 at 8:49:44 AM UTC-7, Tony Mechelynck wrote:
> 1. Which featureset? That can be found from one of the next few lines
> in the :version output after the two you quoted; the line which ends
> with "Features included (+) or not (-)". What does that line say
> before that?
VI
I use pathogen as my plugin manager and updated vim yesterday (via a PPA that
is updated two or three times a week.) When I start vim I now get this error:
Error detected while processing function
pathogen#infect[8]..pathogen#interpose[12]..pathogen#is_disabled:
line5:
E15: Invalid expressi
On Thu, May 25, 2017 at 09:14:06AM +0200, Christian Brabandt wrote:
> So perhaps we need a similar change here as well. Can you provide a
> reproducible example for the :cexpr case please)?
Sure; same setup as before, and in vim:
:cexpr system('ls * \| xargs -n1 -I{} echo {}:1:{}&
On Wed, May 24, 2017 at 11:08:58PM +, Antony Scriven wrote:
> On May 24, Frew Schmidt wrote:
>
> > [...]
> >
> > Maybe a dumb question, but why would BufNew be more expensive
> > than BufRead? Shouldn't the filetype stuff get run either way?
> >
I'm glad you were able to come up with a solution! So I guess `vim *` goes
through a different codepath than `:args *`? Note that this also affects the
quickfix, the location list, and the local args list. Initially I discovered
this issue with `:cexpr` and reproduced it with `:lexpr` and `:a
ay 24, 2017 12:52 PM, "Christian Brabandt" wrote:
>
> On Mi, 24 Mai 2017, fREW Schmidt wrote:
>
> > It is sorta weird that the vb syntax, is somehow part of the problem,
> > but whatever I understand that this was the wrong way to configure the
> > editor.
>
BufRead is only triggered for the first
> one that's actually edited. FWIW 'BufNew' is not in the template
> ftdetect file in the docs. --Antony
>
> On 23 May 2017 at 22:28, Frew Schmidt wrote:
> > On Tuesday, May 23, 2017 at 12:58:16 PM UTC-7, Bram Moolenaar wrote:
>
file in the args list, whereas BufRead is only triggered for the first
> one that's actually edited. FWIW 'BufNew' is not in the template
> ftdetect file in the docs. --Antony
>
> On 23 May 2017 at 22:28, Frew Schmidt wrote:
> > On Tuesday, May 23, 2017 at 12:58
k this yourself I get it. I have multiple
workarounds at this point.
Thanks,
fREW Schmidt
--
--
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
---
On Tuesday, May 23, 2017 at 9:40:02 AM UTC-7, Frew Schmidt wrote:
> On Tuesday, May 23, 2017 at 9:16:45 AM UTC-7, Frew Schmidt wrote:
> > > Perhaps you can get some more information by setting 'verbose' to a
> > >
> > > non-zero number, e.g. ten.
> &g
On Tuesday, May 23, 2017 at 9:16:45 AM UTC-7, Frew Schmidt wrote:
> > Perhaps you can get some more information by setting 'verbose' to a
> >
> > non-zero number, e.g. ten.
>
>
> Well, I ran it with -V10 and even after deleting both ~/.vim/ (except for the
> Perhaps you can get some more information by setting 'verbose' to a
>
> non-zero number, e.g. ten.
Well, I ran it with -V10 and even after deleting both ~/.vim/ (except for the
ftdetect file) and ~/.vimrc and I can still reproduce it. It looks about the
same as before: the markdown support
1:52 AM, "Bram Moolenaar" wrote:
>
> Frew Schmidt wrote:
>
> > I recently discovered that using ftdetect is absurdly slower than
> filetype.vim. To reproduce, try this:
> >
> > mkdir -p ~/.vim/ftdetect
> > echo 'autocmd BufNew,BufNewFi
FYI I reproduced this with a recent checkout and also a 7.3 build, so I'm
pretty sure it's neither fixed nor a regression. I will look into profiling
the issue, but I am still baffled.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text
I recently discovered that using ftdetect is absurdly slower than filetype.vim.
To reproduce, try this:
mkdir -p ~/.vim/ftdetect
echo 'autocmd BufNew,BufNewFile,BufRead *.md :set filetype=markdown' >
~/.vim/ftdetect/markdown.vim
mkdir testing
cd testing
touch {1..500}.
I'm using gvim, as I have for many years, for long-lived editing sessions. I
recently upgraded to ubuntu 17.04 which brought along an upgrade to Vim 8.0.
I have noticed that gvim gets slower and slower with use, and it doesn't seem
to require very much use for it to be, in my opinion, unusably
On Wednesday, May 11, 2016 at 12:17:03 PM UTC-7, Dominique Pelle wrote:
> Frew Schmidt wrote:
>
> > On Wednesday, May 11, 2016 at 2:18:31 AM UTC-7, Dominique Pelle wrote:
> >> [ ... ]
> >> Thanks. I should add: asan writes errors (if any) on stderr by defaul
On Wednesday, May 11, 2016 at 2:18:31 AM UTC-7, Dominique Pelle wrote:
> [ ... ]
> Thanks. I should add: asan writes errors (if any) on stderr by default,
> and since vim puts the terminal in cooked mode, asan error can be
> garbled. So it's best to redirect stderr. The ASAN_OPTIONS
> environment
On Tuesday, May 10, 2016 at 11:03:45 PM UTC-7, Dominique Pelle wrote:
> Frew Schmidt wrote:
>
> > Ok, so I built and installed a fresh vim according to
> > Dominique's instructions and attempted both asan and valgrind.
> > Either those things don't wor
Ok, so I built and installed a fresh vim according to Dominique's instructions
and attempted both asan and valgrind. Either those things don't work together,
or I can repro the bug immediately. Here's the error:
==140331==Shadow memory range interleaves with an existing memory mapping. ASan
c
Thanks all for the replies. I will try Dominique's method of building a new
vim. Note that this issue is *very* rare, maybe happens every few weeks, so I
do not expect it to happen again quickly, nor do I expect to run vim under
valgrind constantly.
For those who might be interested, my confi
any, many plugins stop
working, I expect that I won't be able to keep going on with it.
I am happy to run gdb commands on the coredump, but I cannot send it
as I was editing work code at the time, and besides it's 125 megs.
Let me know how to proceed.
--
fREW Schmidt
https://blog.a
On Fri, Apr 17, 2009 at 1:50 PM, fREW Schmidt wrote:
> I love vim's autoindent, but for some reason it doesn't indent when I type
> [. Is there a way to set that up?
>
I've attached perl and javascript indent files with support for [ on indent
around
for perl. Is there any way I can have this only exist for javascript? I
tried putting syn match Error ..., but that didn't work. Any ideas?
--
fREW Schmidt
http://blog.afoolishmanifesto.com
--~--~-~--~~~---~--~~
You received this message from the &qu
I love vim's autoindent, but for some reason it doesn't indent when I type
[. Is there a way to set that up?
--
fREW Schmidt
http://blog.afoolishmanifesto.com
--~--~-~--~~~---~--~~
You received this message from the "vim_use" maillist.
paces because it has both a paren and a brace.
Does anyone know a way to make it work like it's reading my mind?
Thanks either way!
--
fREW Schmidt
http://blog.afoolishmanifesto.com
--~--~-~--~~~---~--~~
You received this message from the "vim_use&qu
On Tue, Apr 7, 2009 at 9:35 AM, fREW Schmidt wrote:
> > >> >> Maybe this will give some insight: doing @; gives errors about
>> an
>> > >> >> invalid register ';' but doing @: is (apparently) a no-op.
>> > >>
as the one least likely to hold
> "valuable permanent data".
> 2. The above is for use in a mapping. To try it directly at the
> command-line, use | instead of and hit the Enter key (to execute
> the ex-command) instead of .
>
This is close! The first choice works once:
:let @@ = @: exe @@
But then of course @: has changed so I have to do exe @@. I can live with
that for now, but I'd still prefer that the @@ actually included a ; and a
so that I can just do @@ instead of ;exe @@. Of course I'll do it
with a mapping, but hopefully I won't have to do that forever and I'd like
to do this the real vim way.
Thanks again for your help Tony! I'll make mappings now.
--
fREW Schmidt
http://blog.afoolishmanifesto.com
--~--~-~--~~~---~--~~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
On Sun, Apr 5, 2009 at 11:01 PM, Ken Bloom wrote:
>
> On Sun, 05 Apr 2009 22:32:56 -0500, fREW Schmidt wrote:
>
> > On Sun, Apr 5, 2009 at 4:08 AM, Tony Mechelynck <
> > antoine.mechely...@gmail.com> wrote:
> >
> >
> >> On 05/04/09 03:51, Ken
On Sun, Apr 5, 2009 at 4:08 AM, Tony Mechelynck <
antoine.mechely...@gmail.com> wrote:
>
> On 05/04/09 03:51, Ken Bloom wrote:
> > On Fri, 03 Apr 2009 16:04:36 -0500, fREW Schmidt wrote:
> [...]
> >> Maybe this will give some insight: doing @; gives errors about an
On Sat, Apr 4, 2009 at 8:51 PM, Ken Bloom wrote:
>
> On Fri, 03 Apr 2009 16:04:36 -0500, fREW Schmidt wrote:
>
>
> >> > Ok, I figured out what the problem is, but it's a drag because I like
> >> > the setting to much to not use it:
> >> &g
suspect it's
> either operator-pending or command-line that's missing to make it work
> the way you want.)
>
I tried this (with and without the iunmaps) and didn't have any luck.
Thanks anyway Tony.
Maybe this will give some insight: doing @; gives errors about an invalid
r
;
So I can't do @: because it tries to do @; but if I do @; nothing happens at
all...
--
fREW Schmidt
http://blog.afoolishmanifesto.com
--~--~-~--~~~---~--~~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
a
> build compiled with "+cmdline_hist".
If I can do : then I do right? Because I can...
Could it be something weird with my vim configuration? I use @ all the
time for regular macros...
--
fREW Schmidt
http://blog.afoolishmanifesto.com
--~--~-~--~~~--
Ok, so I want to repeat a previous :command. Someone in the IRC channel
told me to use @:, which makes sense. When I *did* try to do @: nothing
happened. I checked to make sure that what I presumed was in : was (":p)
and it was. Why would this command not work?
--
fREW Schmidt
>
>
> what fonts do you think are better for long hour sessions?
>
>
I use terminus in linux and consolas in windows, both around 8 or 10 in
size.
And I love the InkPot colorscheme. It's not too dark or light.
--
-fREW
http://blog.afoolishmanifesto.com
--~--~-~--~~~
>
>
> On 2009-01-26, fREW Schmidt wrote:
> > I am trying to write a function that will open a few windows for me, and
> one
> > of them is on a different machine via windows share (I am currently on
> > windows.) Is there any way to do this w/o mapping a ne
Hello all,
I tend to run one giant gvim with 4-6 splits in it + the project plugin. I
was wondering if anyone knows of a way to integrate the two? Or should I
just make a function that will go into the project split, close it, and run
mksession, and then on load load the session and then open Pr
I am trying to write a function that will open a few windows for me, and one
of them is on a different machine via windows share (I am currently on
windows.) Is there any way to do this w/o mapping a new drive?
--
-fREW
http://blog.afoolishmanifesto.com
--~--~-~--~~~
>
>
> On 2008-11-20, fREW Schmidt <[EMAIL PROTECTED]> wrote:
> > On Thu, Nov 20, 2008 at 3:11 PM, Tim Chase <[EMAIL PROTECTED]>
> wrote:
> >
> > >
> > > > At some point I knew a command that you could use to paste
> > > > visual
On Thu, Nov 20, 2008 at 3:11 PM, Tim Chase <[EMAIL PROTECTED]> wrote:
>
> > At some point I knew a command that you could use to paste
> > visually selected text (or something along those lines) into
> > the ex command box. I couldn't find it in the docs but I
> > presume I didn't know where to l
Hello All,
At some point I knew a command that you could use to paste visually selected
text (or something along those lines) into the ex command box. I couldn't
find it in the docs but I presume I didn't know where to look. Any tips?
Thanks!
-fREW
--~--~-~--~~~---
On Mon, Oct 27, 2008 at 10:31 AM, François Ingelrest <
[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> Anyone else using the latest Ubuntu 8.10? I've installed it this
> week-end, and compiled the latest Vim as well (7.2.25).
>
> I've been using Vim all the day, and the GUI version is quite slow.
> Well
So one of my coworkers just got mad at me for polluting a bunch of source
code with fold markers, so I figured I should investigate syntax based
folding. The folding that comes out of the box for perl is mostly great.
Anyway, I want to fold on anonymous subroutines as well as regular subs.
For ex
47 matches
Mail list logo
