On Friday, December 10, 2021 at 10:07:25 PM UTC+13 cbl...@256bit.org wrote:
>
> Patch 8.2.3615 has been amended a bit by Patch 8.2.3754 so please check
> latest version if this is still problematic for you.
>
Yes, after 8.2.3754 the problem ended. I was unlucky in that my vim update
cadence
have to be reformatted.
Turning off cindent is a fix, but the files have source code in some
elements and these are affected.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For mor
After reading here, I went back to the 18.04 install, and updated vim to
the latest, and the problem does not occur now.
Regards, John Little
--
--
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
t.
A workaround is to start the gui early, by putting a "gui" command in
.vimrc. Back in 2018 there were a few folks using similar workarounds.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the
> - Ubuntu 18.04 with your Vim 8.1 -- has the issue
>
I wonder why you need Vim 8.1. At
https://launchpad.net/~jonathonf/+archive/ubuntu/vim I see only vim 8.2 for
18.04.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post!
toothpik
>is anyone else getting these when they build?
Yes, see the discussion at
https://github.com/vim/vim/issues/4987
Some part of GTK2 being deprecated by another. There's nothing this
project can do about it, other than giving up on GTK2.
Regards, John Little
--
--
You
ck in, the display got stuck on the splash screen.
I conclude that in 20.04, killing an X server with KDE is buggy.
Regards, John Little
--
--
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 informat
s noticeable.
IMO it's crazy that Vim, despite sourcing over 60 scripts, can start in
less than 100 ms, and the GUI can need much longer than that.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the
yone with KDE plasma
5.18.4, or 5.18, on another distro see this?
What might be the cause of this?
Regards, John Little
--
--
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 h
the problem.
The version on github is 189, dated 2019-10-16. Version 188, which I have
from the Ubuntu 20.04 repository, does not show the problem. (Neither do
versions 125, 133, or 179, which I had lying around.)
HTH somebody, and regards,
John Little
--
--
You received this message from
pboard support will not work, though. For editing
files on a server, it may be easier to run vim locally, and use netrw to
access the files.
HTH, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replyin
, store pointers and
allocate each scriptitem_T separately. Also avoids that the
growarray pointers change when sourcing a new script.
HTH, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to
I reproduced this, and noticed that the stock Ubuntu version did not, so
bisected to find the first bad commit is
9c27b1c6d140ca824a78654c1cb70a43a69b4ec6
Date: Sun May 26 18:48:13 2019 +0200
patch 8.1.1400: using global pointer for tab-local popups is clumsy
Problem:Using global pointer f
.txt and version8.2.txt, since support for 8.3
filenames is no longer needed.
Separating the discussion about each significant release from the list of
patches would be sensible too. I imagine that would make maintaining them
easier.
Regards, John Little
--
--
You received this message from the
Just noticed that :help patches gives version8.txt, which lists all the
patch descriptions since 7.4.1, 6,600 of them, but stops at 8.1.2424;
there's no list for the 50 or so 8.2 patches.
Now, version8.txt has become unwieldy; at 1.6 MB it's by far the largest
file in the repo, and github gru
'd be surprised), or the debian or Ubuntu packagers patched it.
Regards, John Little
--
--
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
a: is a scope, like g: or s:, for arguments of the function. For example:
function WithArgs(first, second)
echo a:first a:second
echo a:1 a:2
endfunction
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply belo
tmux.
Or conceivably, no idea if this would work, enable X forwarding with ssh,
run a vim with +X11 and use set mouse=a in vim, then map the scroll events
to .
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text
ing a key down can cause a hang while a key buffer-full of beeps
play. I wonder if any such systems are still used or supported. With
libcanberra repeating a sound just restarts it and sounds play asynchronously
anyway.
Regards, John Little
--
--
You received this message from the &qu
On Sunday, June 9, 2019 at 3:20:23 AM UTC+12, Paul Jolly wrote:
> > Why not just use :self markdown. and a markdown syntax file?
>
> Apologies, I'm probably missing something obvious here; but what is
> the :self command?
The obvious typo, surely :setf markdown?
te sound theme. The large majority who want nothing to do with
sound can continue in their silence, or maybe flash their RGB, or send a
command to an odour generator ;).
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your r
ves me a 100 ms cowbell.
It's only about 15 lines of C. Managing (choosing, distributing) the sound
files would be a far larger task than the code I imagine.
I've no idea about libcanberra on MS Windows.
Regards, John Little
--
--
You received this message from the "vim_dev&quo
I suggest making your changes in your own git branch. My workflow is
git checkout master
git pull
git checkout john
git merge master
I find this cleaner and more flexible than git stash.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your r
~
Running make -j subsequently had no trouble, nor did make reconfig. It seems
that indent.o should now depend on osdef.h; running make depend regenerated
that part of src/Makefile with that dependency for indent.o, and the problem
resolved.
Perhaps make depend should be run on the master.
Reg
adline is used for SSDs and cfq for hard discs.
What does
cat /sys/block/sdb/queue/scheduler
say? If it says something like
noop deadline [cfq]
You might try
echo deadline | sudo tee -a /sys/block/sdb/queue/scheduler
Regards, John Little
--
--
You received this message fro
Solution: Use generic redrawing methods.
Regards, John Little
--
--
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
defined variable: b:is_bash then the code has not been
recognized as bash.
Note that setting is_bash doesn't have an effect immediately, only after a
reload or otherwise re-executing the syntax script, by, say, turning syntax off
and on.
Regards, John Little
--
--
You received this mess
he dot.
> FWIW, :set gfn=Bistream\ Vera\ Sans\ Mono\ 8 gives me correctly placed
> composing characters in gvim with GTK2.
(That's very small.) With that font in vim the dot is under the c but at the
right of the cell. I suggest checking a larger size of that font.
Regards, John Li
tion/LiberationMono-Regular.ttf
100
Regards, John Little
--
--
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 su
us character o.
The same text in Kate, the Kubuntu default editor, puts the dot under the next
character (the r above), in all the fonts I tried. So does Konsole, but xterm
renders it correctly. gedit, the GNOME editor, also shows the dot correctly in
all the fonts I tried.
Weird.
Regards, J
ppose we should just ignore these warnings. Other projects are doing this.
So, if one wants to use -Wextra, I suggest adding -Wno-cast-function-type as
well.
Maybe the comment line in the Makefile could be changed.
Regards, John Little
--
--
You received this message from the "vim_dev&q
ds to be removed so that the user's themes and styles and so on
are allowed to work. The present code guarantees inconsistency, at least on my
screen. Of course, it can't be as easy as that, and I am by no means even
slightly proficient with this stuff.
Regards, John Little
--
--
You r
r 16 has always annoyed me, so I've been reducing this in my
builds of gvim for a long time. Fixing this border width glitch fits well with
the thinner scrollbar.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply
mess.
I suppose that using a block selection for part of a line that is wrapped with
'linebreak' is marginally useful so this problem is very minor.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply belo
wrong with your iconv
library; I suggest reinstalling it, or removing it.
Regards, John Little
--
--
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
ould use this if it gets a SIGCONT it's not expecting.
However, the best approach might be, don't do that. IIUC SIGSTOP can't be
caught, blocked, or ignored and if vim has the X selection other processes that
ask for it will hang.
Regards, John Little
--
--
You received this mes
matchparen.vim plugin. Does it still occur with
vim --clean -N -c 'ru plugin/matchparen.vim' 2.sh
If it does, can you tell us what is in the line in matchparen.vim for which the
error is reported? My line 78 is blank.
Regards, John Little
--
--
You received this message from the &q
ed as the spawn of Satan they are.
Regards, John Little
--
--
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 beca
I see your behaviour with vim --clean -c 'set cinoptions+=L' -c 'normal ggVG='
The in-built C indenting doesn't cope with the opening brace on the same line
as the label. Neither does 'smartindent'.
Regards, John Little
--
--
You received this message from
beasts.
You could try using
CONF_OPT_GUI = --enable-gui=gtk3 --disable-gtktest
in the Makefile to skip some of those GTK tests. The version will still gets
checked, but it's seems bit redundant in that a version less than 3.0.0
wouldn't be, well, 3.
HTH, and regards, John Little
I think these have the same cause as the problem reported by Petr Vorel:
https://groups.google.com/forum/?hl=en#!topic/vim_dev/GB0OXwfTsdA
If your problems are not avoided by
:set t_BE=
to turn off "bracketed paste" then I imagine it's different.
Regards, John Little
--
-
> Observation : gvim shows the "Press enter" line, while vim does not.
I get the opposite; gvim does not show the prompt, vim does.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you ar
ipt_id=1506
Using it might solve your problem, but if it doesn't, it's quite simple, you
could adapt it to suit your needs in a few lines of vim script. However, I
don't know a good way to abort loading the file, perhaps someone here can tell
us.
Regards, John Little
--
On Sunday, July 1, 2018 at 2:28:04 AM UTC+12, Bram Moolenaar wrote:
> Patch 8.1.0128
Just noticed version.c on github doesn't have patch number 128. No effect,
other than a little confusion.
Regards, John Little
--
--
You received this message from the "vim_dev" maillis
uce the flicker.
Regards, John Little
--
--
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 subscr
the end of the paste and the result is a mess.
Regards, John Little
--
--
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 mess
FWIW, using ps (and top and htop) I see a similar result as you, on Kubuntu
18.04 and vim 8.1.0026. (I was deceived for a while by KSysGuard, the KDE
system monitor, showing only 8%, but I think that KSysGuard is dividing by the
cpu count.)
--
--
You received this message from the "vim_dev"
Kazunobu Kuriyama said:
>For the record, this issue isn't due to Vim or GTK+ 3, but the icon theme that
>doesn't comply with the specs.
>...the directory layout of Breeze...
Thank you for that explanation. I've been mystified by some icon behaviour in
another context with GTK 3.
--
--
You
On Wednesday, March 7, 2018 at 11:39:36 AM UTC+13, lkintact wrote:
> Copy this text into the buffer: Тٌам (these are Cyrillic letters with an Arab
> symbol above the "а", probably a result of a poor OCR)
> Move the cursor from "м" to "Т" and back several times. The Arab symbol
> appears and disap
he comment in
x_error_handler in os_unix.c:
/* Silently continuing might be an alternative... */
and commenting out the preserve_exit() call.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For
e gvim failure. For me, any
text file large enough, about 5000 lines, causes gvim to exit if one tries to
ggVG. In the vim source directory, eval.c is not big enough, but cat e*.c > x.c
makes a file big enough.
Regards, John Little
--
--
You received this message from the "vim_dev"
I can reproduce this with 7.4.1689, 7.4.2161, and 7.4.2321, all with GTK2 on
KDE with plasma 5.
I'll have a go later with debug, valgrind and asan.
--
--
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 informa
t looks generic.
Regards, John Little
--
--
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
t -lX11 -lXdmcp -lSM -lICE -lm
-ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl -lcanberra
(Ignore the canberra stuff, I don't like the GTK bell so have coded in my own.
Canberra needs -D_REENTRANT.)
HTH, and regards, John Little
--
--
You received this message from the "vim_dev" ma
On Tuesday, June 21, 2016 at 7:13:46 PM UTC+12, Tony Mechelynck wrote:
> On Mon, Jun 20, 2016 at 3:46 AM, John Little wrote:
> [...]
> > I'm on a debian-derived distro, [...]
>
> Then you may have one bit of useful information. Which command would
> you run using ap
To mention the obvious just in case, are you running (in the vim src)
make reconfig
Sometimes that's necessary due to OS updates, without vim changing.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below t
4-linux-gnu/pkgconfig/gtk+-2.0.pc is an installed file of package
"libgtk2.0-dev".
Regards, John Little
--
--
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/
The GTK check uses the "pkg-config" command. I suggest you look in the
generated "configure" script in the auto directory to see what parameters it is
being given, then run it yourself, and report the parameters and result here.
Regards, John Little
--
--
You received t
es:
configure:2993: checking whether the C compiler works
I conclude that those errors are not your problem. You may have concluded the
same, since --enable-rubyinterp has nothing to do with that part of configure's
processing.
Regards, John Little
--
--
You received this message from
1236kB, file-rss:160kB
The point I'm trying to make is that if you ask vim to do stuff beyond the
resources of the system it's running on, vim will try, and the failure depends
on that system. IMO it would be very difficult to code vim to reliably catch
all the ways it can
nset. Maybe the fix didn't get to XFCE by 14.04, or you are
using something else. Anyway, you could check if DESKTOP_STARTUP_ID is set,
and unset it in your .profile or .bashrc.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post!
On Monday, January 18, 2016 at 9:36:17 PM UTC+13, LCD 47 wrote:
> On 17 January 2016, John Little wrote:
> > Or, would I be better with the cryptic commands above? (I say cryptic
> > because '... use "--set-upstream-to". Something like ...' followed by
> &
t checkout recently. This is a nuisance in that I have
to do it every time.
Regards, John Little
--
--
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
--
l: Exiting because of an unresolved conflict.
$ git commit -a
[master 589478d] Merge remote-tracking branch 'refs/remotes/origin/master'
How should I make this runtime/doc/tags stuff go away? .gitignore doesn't.
Or, would I be better with the cryptic commands above? (I say cryptic be
l: Exiting because of an unresolved conflict.
$ git commit -a
[master 589478d] Merge remote-tracking branch 'refs/remotes/origin/master'
How should I make this runtime/doc/tags stuff go away? .gitignore doesn't.
Or, would I be better with the cryptic commands above? (I say cryptic be
Tony
I have used git checkout to back out my change, as patch 1038 does it now.
Regards, John Little
--
--
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/ma
my local ubuntu archive mirror has packages only for 2.30.7, 2.31.3
and 2.32.[12] for ubuntu and debian. 2.30.7 comes with the long term support
release (supported till 2019) which does not give the deprecation warning. So,
in the debian world only 2.31.3 is widely used.
Regards, John Little
--
in my
post above, change line 2511 of src/configure.in to read
$gdk_pixbuf_version_minor -ge 31 ; then
and make reconfig.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
On Saturday, January 2, 2016 at 7:09:58 PM UTC+13, Tony Mechelynck wrote:
> the compiler warning in question is still there at the current patchlevel.
What does
pkg-config --modversion gdk-pixbuf-2.0
say on your system, Tony?
Regards, John Little
--
--
You received this message from
t once.
Whether anything should be done about this is debatable, but I thought I'd
mention it. Certainly the documentation referred to in the pull request
suggests that GResource landed in 2.32, and my gio/gresource.h has lots of
GLIB_AVAILABLE_IN_2_32 error macros.
Regards, John Little
On Wednesday, November 18, 2015 at 8:09:25 AM UTC+13, John Little wrote:
> FWIW, I don't see this with KDE 5.
>
Just had the opportunity to check this with LXDE on Lubuntu, and I still don't
see it.
Regards, John Little
--
--
You received this message from the "vim_dev&
the wrong parts
of the text being highlighted.
I suspect your problem may have something to do with "extended coordinates".
What does
set ttymouse?
tell you?
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type you
rks: 5.9.0, konsole 3.0.1. on Kubuntu
Regards, John Little
--
--
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 b
FWIW, I don't see this with KDE 5.
Just speculating, this might be caused by a problem with GTK2 in Gnome 3; I
have the impression that the Gnome project does that sort of thing.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-
output.
IMO, the code should explain why this magic number character is used. Then
we'd know how to pick another, maybe.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For
Note also that you can add a full reset when vim starts by putting the
following in your .vimrc:
let &t_ti = "\ec" . &t_ti
I haven't tested that much though. It messes with the "alternate screen"
handling.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type yo
On Sunday, November 8, 2015 at 12:03:49 PM UTC+13, Random832 wrote:
> When running in xterm (a real xterm, not any other terminal reporting
> itself as "xterm") with TERM set to xterm, Vim puts the terminal in a
> state where the screen clearing commands \e[K and \e[J do not work
Are you sure it's
udo apt-get install build-essential
before trying to compile vim.
Regards, John Little
--
--
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
-
On Wednesday, September 9, 2015 at 6:10:24 AM UTC-5, Josh G wrote:
> I keep getting crashes now when opening large file (4GB, 9GB).
+1 for the LargeFile plugin. Though, vim does everything in memory, if you
have less RAM than the size of the file it will be swapping and so slow.
> it kept movi
get the same trouble at the bash
prompt if I run
echo "THUMBS UP SIGN (👍)1234"
then go back and edit the line; vim is not involved.
But it's really a fundamental limitation in vim; it really wants characters in
single cells, with some limited hacks for double width character
On Tuesday, July 21, 2015 at 9:25:55 AM UTC+12, Yuri Vic wrote:
> I came across this symbol: U+1F44D THUMBS UP SIGN (👍)
> In vim-7.4.778 it shows with width one or two...
And Zyx replied:
So this problem has nothing to do with Vim.
I agree. Using "Liberation Mono" with a GTK vim the thumbs up is
gcc 4.9.2 still gives a warning:
ops.c: In function ‘do_addsub’:
ops.c:5406:10: warning: ‘startcol’ may be used uninitialized in this function
[-Wmaybe-uninitialized]
int startcol;
^
AFAICT it's not a problem, but I'm not surprised gcc can't figure that out.
Regar
ack of imagination of what it
might be like to be in other shoes.
Regards, John Little
--
--
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
---
Yo
vertheless, shell script syntax
highlighting is almost a Sisyphean task, and I'm very grateful that Dr Chip has
done it.
Regards, John Little
--
--
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 in
ot valid posix syntax, isn't it?
Indeed, that's ksh syntax; with ash it accepts it but includes an extra $
character. The correct syntax with my ash is
CR='\r'
NL='\n'
In this case flagging the $ as an error is useful, with my ash at least.
Regards, John Little
--
--
suspect you've
really got an Almquist shell. Note that vim's help in syntax.txt says
posix: (using this is the same as setting is_kornshell to 1)
let g:is_posix = 1
but my reading of syntax/sh.vim suggests this is no longer quite true.
Regards, John Little
--
do it; sh.vim notices that /bin/sh resolves to /bin/dash on my
Debian based distro, and sh.vim sets a POSIX flag. Indeed, my distro only has
POSIX shells AFAICT.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply be
a /root for this purpose, perhaps yours doesn't, or
$HOME is screwed up. Looks odd anyway.
So, do you see this not logged on as root? What's your OS, anyway?
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply
On Friday, February 27, 2015 at 11:44:01 AM UTC+13, John Little wrote:
> Though these days gvim is subtracting 1 from the lines I tell it, either with
> -geometry or set lines, I don't know why.
I just looked into this, and I suspect there's a race condition in the GUI. I
ha
x27;gvim -geometry 80x60'
Though these days gvim is subtracting 1 from the lines I tell it, either with
-geometry or set lines, I don't know why.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text y
ff to me.)
Regards, John Little
--
--
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 Googl
with vim, I imagine you'd need a font that
draws it all inside the character cell.
Regards, John Little
--
--
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.
hed, but a couple of initializers
wouldn't hurt, I'd have thought.
Regards, John Little
--
--
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/maillis
nd line is marked.
I see this in 7.4.580, linux amd64. In fact, the \%>Nv atom looks quite
broken, given the line, and vim -u NONE -N:
abcdefgh
\%>2vc and \%2vd work, but \%>2ve does not. More generally, \%>Nv does not
match beyond N + 2, and it used to.
Regards, John Little
--
--
le 2.13.2 here, and no problem. Have you checked with vim -u
NONE?
Regards, John Little
--
--
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
---
Y
, none of them has a
> clipboard manager.
Clipit is reported to work with i3 (in the i3 FAQ), and clipman works with XFCE.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For m
h LXDE one
can install "parcellite", if I've got that correctly.
Regards, John Little
--
--
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/maill
On Thursday, September 11, 2014 4:58:15 PM UTC+12, Dominique Pelle wrote:
> John Little wrote:
> > *** buffer overflow detected ***: vim terminated
...
> I'm guessing you're using Ubuntu.
Well, my post did say Kubuntu.
> Ubuntu modified
> their version of gcc to de
idea that there's an explicit ok for this sort of thing.
Regards, John Little
--
--
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 r
more tests, including platform specific rendering
tests.
As it is, there are many who build vim on their own environments who pull
frequently, and report problems to this list promptly.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type
1 - 100 din 247 matches
Mail list logo
