breviate] n[ext]
So it seems like there needs to be a mechanism to opt out of this
syntax for your case.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your
system I can find
> > /usr/lib/x86_64-linux-gnu/libXm.a
> >
> > The check hasn't changed for a long time. It can be found in
> > src/configure.ac around line 2960.
>
> According to the YaST installer, openSUSE Tumbleweed package libXm4
> titled "Motif ru
the Debian maintainers (Is that just you, James? Thanks for your
> long-time support in Debian):
Currently, yes. :) I used to have more co-consipirators, but they moved
on to other things (at least one to emacs).
> it would be nice to have a gtk version
> without all the externa
patch 9.0.0220, the first patch where problems
> ensued
>
> struggling...
The build only tries to use stropts.h if configure detected that the
file exists. Maybe it existed before your upgrade and no longer does,
so you need to re-configure the Vim build. Try "make reconfig".
>
> Note that I know how to build and install the latest version of Vim.
>
I'll be updating the package in Debian soon. I've had other things on my
plate recently.
Cheers,
James
>
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Ty
is
> + careted or appended to. Only useful for testing, to avoid
s/careted/created/
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply bel
.
This also makes me wonder whether the other uses of bt_normal() should
be reviewed to see if more of them should also apply to buftype=acwrite.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message from the "vim_dev" mailli
tDirectoryInExePath was a
standard Windows thing. Thanks!
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
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
o add Vim's directory to their path, they
already have a means to do that -- their vimrc. Why should Vim be doing
it?
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! T
> > What is different on your system?
>
> You're using gtk-3. I have gtk-2.
They were added in GDK 2.24 and gtk_widget_get_window was added in GTK
2.14, in case someone wants to make a patch with proper version
checking.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7
On Sat, Mar 12, 2022 at 06:40:48PM +, Bram Moolenaar wrote:
> James McCoy wrote:
> > > Is there a good reason to not want the Motif version, or does this just
> > > require some encouragement for someone to setup the packages?
> >
> > Since people do seem to s
On Sat, Mar 12, 2022 at 10:59:57AM +, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > > > Patch 8.2.4527
> > > > Problem:The Athena GUI is old and does not work well.
> > > > Solution: Remove the Athena GUI from c
ackages=vim-athena%2Cvim-common&show_vote=on&from_date=2022-03-01&beenhere=1
[3]:
https://qa.debian.org/popcon-graph.php?packages=vim-athena%2Cvim-gtk3&show_vote=on&from_date=2022-03-01&beenhere=1
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
-
arn-github-actions/workflow-syntax-for-github-actions#concurrency
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying
On Sun, Dec 05, 2021 at 08:17:43PM +, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > On Sun, Dec 05, 2021 at 07:11:00PM +, Bram Moolenaar wrote:
> > >
> > > Patch 8.2.3748 (after 8.2.3747)
> > > Problem:Giving an error for an empty sig
e the error has been reverted, the original issue reported in
https://github.com/vim/vim/pull/9280 still stands -- this creates a
highlight group with an empty string for a name. Should that be
addressed, as was proposed in the PR?
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23
On Sun, Dec 05, 2021 at 06:38:39PM +, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > Why? That complicates the plugin code the same way as dealing with this
> > patch already would. Whether a certain attribute is being defined or
> > not by the plugi
On Sun, Dec 05, 2021 at 05:43:17PM +, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > On Sun, Dec 05, 2021 at 01:03:15PM +, Bram Moolenaar wrote:
> > >
> > > Patch 8.2.3743
> > > Problem:":sign" can add a highlight group wi
his patch causes plugins, like Signify, to error now.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
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 informatio
u': '('.h.')'}}))
> + endif
> + endfor
> + return res
> + endif
> + endfunc
> +
> + if has('patch-8.2.3520')
Why not use "exists('+thesaurusfunc')" here? IMHO, patch numb
> the :g/./d command in vim became faster (~ 2 sec).
>
> I then realized that the Vim command :g/./d copies
> each line that it deletes to the clipboard. And somehow
> the clipman applet made copying to the clipboard slower.
This was supposed to be addressed by 7.4.396, which defers u
On Sat, Mar 06, 2021 at 11:39:14AM +0100, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > Shouldn't the tests use CheckNotRoot() so they're skipped?
>
> I've been wondering what the best approach is:
> - Just let the tests fail, tell the user th
Shouldn't the tests use CheckNotRoot() so they're skipped?
On Fri, Mar 5, 2021, 14:48 Bram Moolenaar wrote:
>
> Patch 8.2.2570
> Problem:Tests fail when run as root.
> Solution: Add a comment mentioning the expected failure. (issue #7919)
> Files: src/testdir/test_edit.vim, src/testdi
t; value. Let me give that a try.
> If that fixes it I do wonder why it doesn't fail on other systems.
> Perhaps because of how the union is laid out (overlapping different
> bytes).
I was about to send a similar patch. That does fix the problem.
Cheers,
--
James
GPG Key: 4096
On Sun, Feb 14, 2021 at 12:58:03PM +0100, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > On Sat, Feb 13, 2021 at 04:23:02PM -0500, James McCoy wrote:
> > > On Sat, Feb 13, 2021 at 07:13:35PM +0100, Bram Moolenaar wrote:
> > > >
> > >
On Sat, Feb 13, 2021 at 04:23:02PM -0500, James McCoy wrote:
> On Sat, Feb 13, 2021 at 07:13:35PM +0100, Bram Moolenaar wrote:
> >
> > Somehow the Travis tests run fail for s390:
> > https://travis-ci.com/github/vim/vim/builds/217016917
> >
> > I do not see
> Does anyone have an idea of how to pinpoint this problem?
I'll see if I can replace on Debian's s390x system.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message from the "vim_dev" maillist.
Do not top-
apt install libgtk2.0-dev
This should really be libgtk-3-dev. GTK+2 has been unsupported for
years and GTK+3 is already going to maintenance mode as work transitions
to GTK+4.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message fr
_arg.type.ct_type = alloc_type(expected);
> ! // Use the negated offset so that it's always positive. Some
> systems don't
> ! // support negative numbers for "char".
> ! isn->isn_arg.type.ct_off = (char)-offset;
>
Or is it that whether char is
e the credits
aren't enough.
The free account also limits the concurrency to a single job at a time,
which is why CI times are taking so much longer now.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message from the &quo
or example, https://github.com/vim/vim/pull/7188.diff
Cheers,
James
>
--
--
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 m
I don't see why it
matters.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
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:
ecated parts of GLib. Since GTK2 is not seeing new
development, this probably isn't going to be fixed. Either accept the
warnings or build with GTK3 instead.
Previously discussed at https://github.com/vim/vim/issues/4987
Cheers,
James
>
--
--
You received this message from the "
On Sun, Mar 15, 2020, 12:19 Yegappan Lakshmanan wrote:
> I think, even in non-gui builds, some of the code path (e.g. clipboard)
> depend on the DISPLAY being set.
>
> I don't know whether this change is relevant to enabling the s390 builds.
> This change should be reverted as this reduces the co
On Sat, Feb 22, 2020 at 04:56:26PM -0500, James McCoy wrote:
> On Sat, Feb 22, 2020 at 09:21:56PM +0100, Bram Moolenaar wrote:
> >
> > James McCoy wrote:
> >
> > > On Sat, Feb 22, 2020 at 9:02 AM Bram Moolenaar wrote:
> > > >
> >
On Sat, Feb 22, 2020 at 09:21:56PM +0100, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > On Sat, Feb 22, 2020 at 9:02 AM Bram Moolenaar wrote:
> > >
> > > Dominique wrote:
> > >
> > > > At https://buildd.debian.org/status/package
oblem, adding "!" would be ignoring
> that problem.
I can reproduce this on the hppa porterbox. Running the test on its
own is fine. It's only when running the entire file that the error
shows up. I'll see if I can narrow down what's causing the problem.
Cheers,
Jam
sion of a shell. It does mention that "which" is widely available,
> > > while "type" is not.
> >
> > FWIW, "command -v ..." is specified in POSIX. "type" is as well, but as
> > an XSI extension.
>
> In tcsh:
>
> $ command -
t great. It doesn't list what command is available in which
> version of a shell. It does mention that "which" is widely available,
> while "type" is not.
FWIW, "command -v ..." is specified in POSIX. "type" is as well, but as
an XSI extension.
Che
set viminfofile=""
" is Vim's comment character, so that command is effectively the same as
set viminfofile=
Do not quote the filename. If there's white space, then you need to
escape it -- see “:help option-backslash”.
Cheers,
--
James
GPG Key: 4096R/91
On Tue, Aug 20, 2019, 09:30 Christian Brabandt wrote:
>
> On Di, 20 Aug 2019, Zdenek Dohnal wrote:
>
> > Hi all,
> >
> > I found out there is Vimx symlink to gvim binary in my Vim package in
> Fedora.
> >
> > Does anyone know what Vimx is/was? What behavior did it have?
> >
> > I see from man pag
On Thu, Jun 13, 2019, 10:43 Paul Jolly wrote:
> Hi all,
>
> I'd like to propose a version() function (or variable I guess?) that
> returns a string that is the semver version of Vim, i.e. v8.1.1518
>
Sounds like you're looking for the v:version variable.
Cheers,
James
SRC_ALL = \
> + .gitignore \
> .hgignore \
> .lgtm.yml \
> .travis.yml \
Why would .gitignore, .hgignore, .lgtm.yml, etc. be in the source
archives? They're only relevant for the VCS repos.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 695
m/vim81/filetype.vim:
line 10:
E319: Sorry, the command is not available in this version: let
did_load_filetypes = 1
line 13:
E319: Sorry, the command is not available in this version: let s:cpo_save = &cpo
line 45:
E319: Sorry, the command is not available in this version: func! s:StarSet
the vim_dev list because I think that this may be a bug
> > > in Vim and that further discussion belongs there.
> >
> > Well, I would think less is to blame to change the escape sequences and
> > not restore it. Vim figures out what codes the cursor keys are sending,
> >
uot; output then?
>
Your patch added my comment and a new test, whereas my patch added a
comment and fixed the regex for the existing test. Ozaki's pointing out
that you forgot to remove the original line.
These sorts of problems would be avoided if the PRs were actually merged,
On Sun, Jan 27, 2019 at 02:29:51PM +0100, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > filetype.vim contains the following:
> >
> > 485 au BufNewFile,BufRead *.comcall
> > dist#ft#BindzoneCheck('dcl')¶
> > …
> &g
f.d/*.conf*
call s:StarSetf('apache')¶
It's not uncommon for apache configuration, especially those under
sites-*/*, to use a filename that matches *.com. In that case, the dcl
filetype will be set rather than apache.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7
(c)
(gdb)
994 if (echeck_abbr(ESC + ABBR_OFF))
(gdb)
1028if (goto_im())
(gdb)
1030if (got_int)
(gdb)
1036vim_beep(BO_IM);
(gdb)
1607if (c != K_CURSORHOLD
(gdb)
1613did_cursorhold = FALSE;
(gdb)
1
s:
user config overrides system config overrides baked-in defaults
The mechanism of using defaults.vim changes that to be
(defaults.vim or user config) overrides system config overrides baked-in
defaults
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
stripping is done?
> Is there a way how to disable stripping during build?
You were on the right track, but you don't need to edit the Makefile.
It can be passed on the command-line -- make STRIP=: install -- which is
exacty what I do in Debian's packaging.
Cheers,
--
James
GPG Key:
->w_lines[0].wl_lnum > wp->w_topline
> > + || !redrawing());
> > +
> > +// redrawing might have processed async messages,
> > +// causing wp to become invalid
> > +if (!win_valid(wp))
> > + wp = curwin;
> > +
On Sun, Nov 25, 2018 at 07:19:52AM +0100, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > On Thu, Sep 13, 2018 at 01:11:44PM +0200, Christian Brabandt wrote:
> > >
> > > On Do, 13 Sep 2018, 'Jonathon Fernyhough' via vim_use wrote:
> > >
&
d
$20 = 1000
(gdb) p curwin
$24 = (win_T *) 0x5628819de9c0
However, the next frame down wp isn't pointing at the same memory and
has garbage:
(gdb) down
#12 0x562880cdf380 in curs_rows (wp=0x562881a4db40) at move.c:752
752 wp->w_cline_row += plines_win_nofill(wp, l
(trying to get more information about the other failures) and stderr
redirected to a file. This was also being run in an automated build
environment, so there was no tty available.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this m
On Sun, Nov 04, 2018 at 08:09:10PM +0100, Christian Brabandt wrote:
>
> On So, 04 Nov 2018, Bram Moolenaar wrote:
>
> > + else if (STRLEN(p_hlg) >= 1 && *p_hlg == 'C')
>
> James mentioned[¹], that this might be overly eager.
This isn't doin
On Saturday, September 8, 2018 at 12:20:42 AM UTC+5:30, Gary Johnson wrote:
> I frequently use vim to read the contents of .tgz files. This has
> recently stopped working. It works fine with my old Vim 7.2.333 on
> Ubuntu and 8.0.1567 on Cygwin, but my newer 8.1.332 on Ubuntu and
> 8.1.347 on Fed
On Tue, Aug 21, 2018 at 09:02:42PM -0400, James McCoy wrote:
> On Tue, Aug 21, 2018 at 08:29:09PM +0200, Bram Moolenaar wrote:
> > *** ../vim-8.1.0312/src/testdir/test_swap.vim 2018-05-12
> > 15:57:33.0 +0200
> > --- src/testdir/test_swap.vim 2018-08-
E563:
> stat(/source/vim/vim-8.1.0315/src/vim-basic/testdir/Xcscopedir/cscope.out)
> error: 2 @ function RunTheTest[40]..Test_cscope_add_dir, line 3
It looks like you're building in a shadow directory. cscope doesn't
follow symlinks, so the test fails to build a database for
../m
sert_match('8\.', info.version)
+ let ver = printf('VIM %d.%d', v:version / 100, v:version % 100)
+ call assert_equal(ver, info.version)
call assert_match('\w', info.user)
call assert_equal(hostname(), info.host)
call assert_match('Xswapinfo', info.fnam
natively supported in Vim.
>
> I mention only about option name.
>
> Option name 'inccommand' is not intuitive.
> I think 'substituteopt' ('subopt' in short name) is better.
It's called 'inccommand' because it's not intended to be
On Mon, Jun 25, 2018 at 12:06:15AM +0200, Bram Moolenaar wrote:
>
> James McCoy wrote:
> > eval_expr_to_bool() handles numbers just fine. Why make supplying a
> > number for the skip argument a hard error instead of simply evaluating
> > it to a boolean?
> >
>
r the skip argument a hard error instead of simply evaluating
it to a boolean?
The documentation had already stated that evaluation of the skip
argument "should return non-zero if this match is to be skipped".
The general reporting of errors instead of ignoring them is definitely
usef
On Sun, May 13, 2018, 10:56 Ken Takata wrote:
> Hi Bram,
>
> 2018/5/13 Sun 23:00:29 UTC+9 Bram Moolenaar wrote:
> > Patch 8.0.1832
> > Problem:Cannot use :unlet for an environment variable.
> > Solution: Make it work. Use unsetenv() if available. (Ken Takata,
> > closes #2855)
most of the places that Vim uses this sort of functionality isn't
actually valid for flexible arrays. Struct with flexible arrays can't
be contained in arrays or in other structs, and Vim does at least the
latter in a number of places.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7
probably be enough for what Vim (and its dependencies) need.
> I just thought about C99 a few days ago, when I saw a colleague
> having a crash with vim, because he did not compile it with
> -D_FORTIFY_SOURCE=1. The ugly compilation option won't
> be needed with C99,
That would certai
now :(
You just got the builds mixed up. :)
12264088 (+vartabs) is larger than 12234272 (-vartabs). The more
interesting figures (if size is really a factor) would be after
stripping both binaries, since that's what most people are likely to
encounter.
Cheers,
--
James
GPG Key: 4096R
org/cgi-bin/bugreport.cgi?bug=787628#15
The browser shouldn't be copying data the user can't see, rather than
making the terminal second guess what the user is pasting.
Cheers,
James
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your r
whitespace around the ‘=’ when setting an option.
Second, Vim's comment character is ‘"’ so even if whitespace were
allowed, this would be setting the options to the empty string.
So, none of these options have been set as you expect. You can verify
this by running “:set luadll?”.
Cheers
ns. Can we make that happen?
When using clang -fsanitize=address, you either need to
to set up ASAN_SYMBOLIZER_PATH env variable as
described here:
It's also supposed to work when llvm-symbolize is in $PATH, which it should
be. PATH is updated just before running the tests.
James
--
--
Yo
sgr. See :help 'ttymouse'. When
'ttymouse' isn't urxvt or sgr, then you run into the 223 column
limitation of the old addressing style.
You should be able to use ttymouse=sgr, assuming you have an xterm
version > 277.
Cheers,
--
James
GPG Key: 4096R/91BF BF
on hurd-386 and alphan platforms.
I'd be glad to sponsor[0] access to the porterboxes[1] if you want to
investigate more. I could also use more help with the Debian packaging
if you're interested in that. ;-)
[0]: https://dsa.debian.org/doc/guest-account/
[1]: https://db.debian.org/mach
erm_sendkeys(g:buf, (h / 3 - 1)."o\")
- call term_wait(g:buf, 500)
+ " Wait for the nested Vim to exit insert mode, where it will show the ruler
+ call WaitFor(printf('term_getline(g:buf, %d) =~ "\<%d,.*Bot"', rows, rows))
call term_sendkeys(g:buf, "Gi
it(g:buf, 500)
+ " Wait for the nested Vim to exit insert mode, where it will show the ruler
+ call WaitFor(printf('term_getline(g:buf, %d) =~ "\<%d,1\>"', h, h / 3))
call term_sendkeys(g:buf, "Gi\")
call term_sendkeys(g:buf, "\")
call ter
s.
[0]:
https://buildd.debian.org/status/logs.php?pkg=vim&ver=2%3A8.0.1226-1&suite=sid
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the te
y not what this thread is about.
Apparently, :q is documented in two places and the place with the :q tag
doesn't mention this behavior. However, it does point you to the other
location (:help CTRL-W_q), which does document it.
Cheers,
James
--
--
You received this message from the "vim_
; moves out of the fold.
It seems like there's an off-by-one issue when the fold is on the last
line of the buffer.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type
> An attacker, requiring no special permissions,
Except the ability to put arbitrary files on your computer. If someone
can get arbitrary content onto your system, then you've already lost.
The "vulnerability" here is that the user put a untrusted file into a
location that Vim e
>
> > > > A simple
> > > >
> > > > ./configure && make && make test
> > > >
> > > > in a clean source tree (meanwhile v8.0.1118) gives the same error.
> > >
> > > What kind of system is this?
> >
er. BufEnter triggers every time
the buffer becomes curbuf. TermOpen only triggers when starting the
terminal.
Cheers,
James
--
--
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
Your misinterpreting the results. You got a 302 redirect, but curl doesn't
follow redirects by default. Use "curl -L" to enable following redirects.
Cheers,
James
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below
a blacklist of patches and
has() rightfully assumes that a greater major version has all the
patches from the previous major version.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message from the "vim_dev" maillist.
D
isible" cursor),
then just send the current cursor shape & 1.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
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
On Aug 17, 2017 09:37, "François Ingelrest"
wrote:
Hi,
On 17 August 2017 at 14:24, James McCoy wrote:
> What exactly are the extra characters you're seeing? At a guess, it's
> something like "[2 q". If so, that's because libvte (until relatively
>
libvte (until relatively
recently) passed through control codes that it didn't understand, which
meant they were printed to your terminal. That particular control code
is the one to control the shape of the cursor.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331
gt; ]12;royalblue2<07>. This one was missing from libvterm, the codes
> you mention might be others that are missing, but what is trying to use
> them?
Isn't the more relevant question "Why is libvterm's DEBUG_LOG enabled?".
Cheers,
--
James
GPG Key: 4096R/91BF BF4D
;
> > > but got '$ correct'
we got text that shouldn't have even been on the same line. This looks
like it transposed the echoed text with the prompt on the next line.
I'll give the updated patches a try and see if that resolves these
problems.
Cheers,
--
James
GPG
'r'
but got ''
function RunTheTest[24]..Test_terminal_scrape_multibyte line 28: Expected 's'
but got ''
I reproduced, during a full build, the Test_terminal_env() on one of the
porter systems I have access to but then it worked fine when I re-ran
test_te
he syntax highlighting for the
document that follows is correct, i.e.
\newcolumntype{C}[1]{>{\hfil\(} p{#1} <{\)\hfil}}
Hope this helps!
James
--
--
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 informati
an. Executable sizes: Huge, 2934944 bytes; Tiny, 766992 bytes. Size
ratio: 3.826564 to 1.)
You're comparing apples and oranges. The right comparison is tiny feature
build without and with FEAT_MBYTE. That comparison, using 8.0.0823, is
838K vs. 978K here.
Cheers,
James
--
--
You received this
current row? That would be
consistent with getline(), line(), getcurpos(), etc.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are rep
work. Thanks.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
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
1]..Test_getcmdtype[15]..Check_cmdline line 3: Expected
'@' but got ''
fill_input_buf() already has its own, less restrictive handling of
environments such as this, which is why the non-GUI enabled builds work.
Given that, the attached patch addresses the issue but I'm not s
an/src/github.com/vim/src/main.c:177
#8 0x7fac1c4d92b0 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x202b0)
SUMMARY: AddressSanitizer: bad-free
(/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc19e0) in free
==19734==ABORTING
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DF
f the :terminal command. Includes
> libvterm converted to ANSI C. Many parts still missing.
Why did you choose to bundle libvterm instead of building against the
system library as is done with all other dependencies?
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 D
That's trivial to
implement with GCC by building with `-fwrapv`, but I'm not sure how many
other compilers provide a similar flag.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--
--
You received this message from the "vim_dev" maillist
On Fri, May 05, 2017 at 10:23:49PM +0200, Bram Moolenaar wrote:
> James McCoy wrote:
> > It would be nice for there to be defined behavior here for the user,
> > instead of exposing them to the whims of the compiler implementation.
>
> Unfortunately, that is quite diff
th a -fsanitize=undefined build by running
if has('num64')
echo float2nr(pow(2, 62)) * 2
else
echo float2nr(pow(2, 30)) * 2
endif
It would be nice for there to be defined behavior here for the user,
instead of exposing them to the whims of the compiler implementation.
Cheers,
On Apr 21, 2017 10:25, "Manuel Ortega" wrote:
On Thursday, April 20, 2017 at 3:05:41 PM UTC-4, Manuel Ortega wrote:
> This patch unfortunately completely wrecks parallel builds on macOS
10.12.4.
As a side note, now that we know that the problem has nothing to do with
parallel builds but affects
On Mon, Mar 20, 2017 at 05:42:44PM -0700, Yegappan Lakshmanan wrote:
> On Mon, Mar 20, 2017 at 4:46 PM, James McCoy wrote:
> > Why keep shoe-horning things into the set{qf,loc}list functions? This
> > just makes it an awkward API to use.
> >
> > I wo
1 - 100 din 694 matches
Mail list logo
