On Sat, Aug 27, 2016 at 08:32:09PM -0700, JohnBeckett wrote:
> Bram recently fixed :diffoff!
> https://groups.google.com/forum/#!topic/vim_dev/h1nREhhF7mY
> That reminds me of a diff frustration.
> Suppose I have two files expected.txt and output.txt, each over 1000
> lines. Running a test
On Sun, Jul 31, 2016 at 12:21:59PM -0700, Elronnd wrote:
> I'm not quite sure how to describe this bug, so I'll just explain how
> to reproduce it. Basically, open vim on a new .txt file (it doesn't
> appear to work for other types of files). Type on open curly-brace,
> enter, close-curly-brace.
On Tue, Jul 26, 2016 at 09:50:33AM -0700, Ricky Manriquez wrote:
> When I type :bd in a tab, I expect to be taken back to the previous buffer,
> not the previous tab
try this:
command! BD b # | bd #
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your
after this latest round of updates configure is no longer able to
successfully detect my gtk2 support -- why would that change?
I don't want to lose gui so I'm going to be stuck at 7.4.2098 until I
get this figured out
--
--
You received this message from the "vim_dev" maillist.
Do not
On Mon, Jun 27, 2016 at 04:00:20PM -0700, allen haim wrote:
> ... fire autocmds on :cd and :lcd family of commands.
> This is intended to fix #868.
> Note that it only responds to user-initiated changes (:cd, :lcd, and
> synonyms); are there other ways the working directory can change that
> we
s and their "development" packages,
> it ought already to be OK.
> Then reconfigure and recompile. See
> http://users.skynet.be/antoine.mechelynck/vim/compunix.htm for
> details.
> Best regards,
> Tony.
> On Wed, Jun 22, 2016 at 3:58 PM, toothpik <toothp...@
ve all
> >> requirements for building Vim with GTK2?
> >
> > sudo apt-get build-dep vim-gtk
> >
> > Regards, John Little
> Thanks. Toothpik, if this exact same command doesn't work for SUSE due
> to the package names being different, then try
>su
On Fri, Jun 17, 2016 at 10:34:34PM +0200, Tony Mechelynck wrote:
> On Fri, Jun 17, 2016 at 2:54 PM, toothpik <toothp...@gmail.com> wrote:
> > On Fri, Jun 17, 2016 at 10:01:14AM +0200, Tony Mechelynck wrote:
> >> On Fri, Jun 17, 2016 at 2:29 AM, toothpik <toothp...@gmai
On Fri, Jun 17, 2016 at 10:01:14AM +0200, Tony Mechelynck wrote:
> On Fri, Jun 17, 2016 at 2:29 AM, toothpik <toothp...@gmail.com> wrote:
> > On Thu, Jun 16, 2016 at 11:59:46PM +0200, Tony Mechelynck wrote:
> >> Check the console output from configure if you still have
On Thu, Jun 16, 2016 at 11:59:46PM +0200, Tony Mechelynck wrote:
> Check the console output from configure if you still have it, or else
> the src/auto/config.log (or src/shadow/auto/config.log if you build in
> a shadow directory) which is more verbose. What exactly does configure
> not find that
suddenly I am having trouble getting config to find either gtk+2 or +3
yast assures me I have the latest gtk2-devel and gtk3-devel
has something changed?
--
--
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
I would reply to my first message if googlegroups would let me see it...
after I posted, the warnings stopped (g)
--
--
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
for a while now, and forgive me for not knowing exactly how long, I've
been getting warnings from GTK every time I start gvim:
-
(gvim:24943): Gtk-WARNING **: Theme directory actions/48 of theme breeze
On Thu, Apr 28, 2016 at 02:25:36AM -0700, Konfekt wrote:
> Thanks a bunch ! Exactly, the definition of MAN_PN is the weak point.
> So after updating instructions for other shells, apparemment BSD is
> unsupported. Could you explain tha ol trick about the removal of
> backspaces that yet works
On Fri, Apr 22, 2016 at 06:51:30AM -0700, W. wrote:
> Steps to reproduce:
> 1. open any file for which vim highlights matching parenthesis
this sounds suspiciously like behavior provided by a plugin -- if, after
you have opened this "any file for which vim highlights matching parens"
you perform
On Fri, Apr 15, 2016 at 02:44:36PM +0200, Christian Brabandt wrote:
> Hi toothpik!
> On Fr, 15 Apr 2016, toothpik wrote:
> >
> >
> > Test results:
> >
> >
> > From test_hardcopy.vim:
> > Found errors in Test_with_syntax():
> > Caught ex
On Fri, Apr 15, 2016 at 02:44:36PM +0200, Christian Brabandt wrote:
> Hi toothpik!
> On Fr, 15 Apr 2016, toothpik wrote:
> >
> >
> > Test results:
> >
> >
> > From test_hardcopy.vim:
> > Found errors in Test_with_syntax():
> > Caught ex
On Fri, Apr 15, 2016 at 02:44:36PM +0200, Christian Brabandt wrote:
> Hi toothpik!
> On Fr, 15 Apr 2016, toothpik wrote:
> >
> >
> > Test results:
> >
> >
> > From test_hardcopy.vim:
> > Found errors in Test_with_syntax():
> > Caught ex
On Fri, Apr 15, 2016 at 02:44:36PM +0200, Christian Brabandt wrote:
> Hi toothpik!
> On Fr, 15 Apr 2016, toothpik wrote:
> >
> >
> > Test results:
> >
> >
> > From test_hardcopy.vim:
> > Found errors in Test_with_syntax():
> > Caught ex
Test results:
>From test_hardcopy.vim:
Found errors in Test_with_syntax():
Caught exception in Test_with_syntax(): Vim(syntax):E484: Can't open
file ../../runtime/syntax/python.vim @ /home/scott/.vim/syntax/vim.vim,
line 724
>From test_matchadd_conceal.vim:
Found errors in
>From test_syntax.vim:
Found errors in Test_syn_iskeyword():
Caught exception in Test_syn_iskeyword(): Vim(syntax):E484: Can't open
file ../../runtime/syntax/python.vim @ /home/toothpik/.vim/syntax/vim.vim, line
724
TEST FAILURE
Makefile:41: recipe for target 'report' failed
make[1]: *** [rep
On Tue, Apr 05, 2016 at 09:56:27PM +0200, Bram Moolenaar wrote:
> Patch 7.4.1713
> Problem:GTK GUI doesn't work on Wayland.
> Solution: Specify that only the X11 backend is allowed. (Simon McVittie)
> Files: src/gui_gtk_x11.c
dunno if it's hurting anything, but building this I get two
On Mon, Apr 04, 2016 at 10:13:17PM +0200, Bram Moolenaar wrote:
> I have been wondering if the next release should be called 7.5 or 8.
my vote would be for 7.5 -- I run vim with option noloadplugins and I
don't [yet] see any significant improvements to how I use it
that said, I noticed you said
I've got a module in which I keep passwords, encrypted with blowfish2 --
recently (and I can't be more specific than that) when I open that file
it opens a completely blank gvim window, where there used to be a
message informing me that the module is encrypted and I need to input
the key
thinking
On Sun, Mar 13, 2016 at 02:34:40PM +0100, Bram Moolenaar wrote:
> Patch 7.4.1556
> Problem:"make install" changes the help tags file, causing it to differ
>from the repository.
> Solution: Move it aside and restore it.
> Files: src/Makefile
thank you!
--
_|_ _ __|_|_ ._
On Mon, Mar 07, 2016 at 12:35:34AM +0900, Kazunobu Kuriyama wrote:
> 2016-03-07 0:15 GMT+09:00 toothpik <toothp...@gmail.com>:
> > On Sun, Mar 06, 2016 at 02:16:56PM +0900, Kazunobu Kuriyama wrote:
> > > 2016-03-06 12:28 GMT+09:00 toothpik <toothp...@gmail.com>
On Sun, Mar 06, 2016 at 02:16:56PM +0900, Kazunobu Kuriyama wrote:
> Thank you for your prompt reply.
> 2016-03-06 12:28 GMT+09:00 toothpik <toothp...@gmail.com>:
> > (gvim:30088): Gtk-CRITICAL **: gtk_distribute_natural_allocation:
> > assertion 'extra_space >=
On Sat, Mar 05, 2016 at 05:54:40PM -0800, nuko8 wrote:
> Thank you for reporting.
> A [patch](https://github.com/vim/vim/releases/tag/v7.4.1497) for
> fixing the issue was included in the upstream master a few hours ago.
> Hopefully, this works for you.
I for one now see proper cursor movement
>= 0' failed
the script that starts the windows can be seen at
https://github.com/toothpik/toothpik-s-.vimrc/blob/master/bin/ws
-tp
--
--
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 info
On Sun, Jan 17, 2016 at 08:39:19PM -0800, John Little wrote:
> On Sunday, January 17, 2016 at 4:59:10 AM UTC+13, LCD 47 wrote:
[snip]
> How should I make this runtime/doc/tags stuff go away? .gitignore doesn't.
a simple
git checkout runtime/doc/tags
will solve the issue [each time it gets
On Sun, Nov 29, 2015 at 10:01:02PM +0100, Bram Moolenaar wrote:
> Christian Brabandt wrote:
> > On So, 29 Nov 2015, Bram Moolenaar wrote:
> >
> > >
> > > Nikolay Pavlov wrote:
> > >
> > > > 2015-11-29 19:36 GMT+03:00 Bram Moolenaar :
> > > >
> > > > >
> > > > > Patch
On Fri, Oct 16, 2015 at 08:17:01AM -0700, Gary Johnson wrote:
> On 2015-10-15, Peng Dai wrote:
> You can use ^+ to prepend a value to a string option:
you fat-fingered that first one -- you meant to say:
You can use ^= to prepend a value to a string option:
--
--
You received this
to be a way to do the
> equivalent in git (mention the file in gitignore and make sure it
> isn't tracked). Maybe "git help" could, well, help you.
> N.B. False friends: "hg fetch" means "git pull" and vice-versa.
> Best regards,
> Tony
> On Thu, S
I used to sometimes have a problem with the tags module when we were
under hg, and I had a specific set of things I did to get around it
it seems the problem has followed us to git -- here's my pull:
Wed 19:30 ~/.build/vim/vim: git pull
remote: Counting objects: 39, done.
remote: Compressing
I'd reply to my first email but google never lets me see my emails,
hence this new one
I took 'make distclean' out of my make script and now myconfig sticks
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For
I have a "myconfig" which deletes src/auto/config.cache then runs
./configure with 3 options, among them --with-compiledby=toothpik@home
since patch 861, make is insisting on re-running config and making up
its own compiledby
interestingly the other two options, --with-featu
On Thu, Jan 22, 2015 at 06:14:43PM +0900, Kazunobu Kuriyama wrote:
On Jan 22, 2015, at 0:15, Kazunobu Kuriyama kazunobu.kuriy...@nifty.com
wrote:
Hi,
On Jan 21, 2015, at 3:01, Bram Moolenaar b...@moolenaar.net wrote:
Patch 7.4.587
Problem:Conceal does not work properly with
On Mon, Dec 22, 2014 at 03:20:09PM -0500, Donald Allen wrote:
I am trying to turn off auto-commenting, completely without success. I
am running vim 7.4.540 on an up-to-date Arch Linux system. My .vimrc:
1 set nocp
2 set shiftwidth=4
3 set tabstop=4
4 set background=light
On Thu, Dec 18, 2014 at 11:18:28AM +0100, Lubos Pintes wrote:
Hello,
We have functions winwidth(winnr) and winheight(winnr).
I thing that winleft(winnr) and wintop(winnr), are missing. Perhaps
I greatly overlooked something, I don't know how to determine where
the window with concrete winnr
On Sun, Oct 26, 2014 at 09:58:29PM +0100, Roland Eggner wrote:
When options breakindent, wrap and vartabstop are used all together, there
are
erroneous indentation offsets of continuation lines, as if
breakindentopt=shift:N would specify nonzero values of N depending on number
of
tab
=Eatchar('\s')cr
iabbrev silent ddss c-r=strftime(%Y-%b-%d %H:%M
%a)crc-r=Eatchar('\s')cr
my whole .vimrc can be seen at
https://github.com/toothpik/toothpik-s-.vimrc/blob/master/.vimrc
most likely I've done something silly and embarrassing so please be kind
when you point it out
On Tue, Oct 21, 2014 at 12:29:54AM +0300, LCD 47 wrote:
On 20 October 2014, Christian Brabandt cbli...@256bit.org wrote:
On Fr, 17 Okt 2014, LCD 47 wrote:
Namely, compare the effect of:
set beval bexpr=['foo']
to the effect of:
set beval bexpr='foo'
On Tue, Oct 07, 2014 at 03:46:56PM +0200, Martin Tournoij wrote:
If you want your own settings and never want to have filetype plugins
enabled, do NOT set the :filetype plugin command in your .vimrc (so
ftplugins are effectively disabled). Alternatively you can override
those settings
On Mon, Oct 06, 2014 at 06:41:21PM +0200, Bram Moolenaar wrote:
Patch 7.4.465 (after 7.4.016)
when I point my browser (firefox) at
https://code.google.com/p/vim/source/browse/src/version.c
to see if 465 is in there all it shows me is 464, and that's what I get
when I update and build
do
On Mon, Sep 29, 2014 at 06:09:23PM +0200, Bram Moolenaar wrote:
Marco Hinz wrote:
win_draw_end() is used to clear the end of the screen in certain
cases, e.g. very long, wrapped lines or the actual end of the buffer.
Fold and sign columns get continued although that's not useful at
how terribly embarrassing -- according to my update.log, no! apologies for the
noise
sc
From: Ken Takata ken...@csc.jp
To: vim_dev@googlegroups.com
Cc: toothpik scott2...@yahoo.com
Sent: Friday, February 1, 2013 1:41 PM
Subject: Re: Patch 7.3.798
Hi
Subject: Re: Patch 7.3.798
On 01/02/13 02:48, toothpik wrote:
for me, version.c was not updated when I pulled this update -- I didn't
expect much since I don't build
for mzscheme, but at least version should have updated
sc
Neither do I (the script I source before building includes the line
7.3.798
Hi toothpik!
On Fr, 01 Feb 2013, toothpik wrote:
I have a script I call u that performs a
cd ~/.build/vim/vim
hg pull 21 ../update.log
I'm also on suse 12.1 -- small world
What does your :version show? The patch included a change to the
version.c file (as you can see
for me, version.c was not updated when I pulled this update -- I didn't expect
much since I don't build
for mzscheme, but at least version should have updated
sc
From: Bram Moolenaar b...@moolenaar.net
To: vim_dev@googlegroups.com
Sent: Thursday, January
49 matches
Mail list logo