Re: [vim/vim] [netrw] Fix file move when g:netrw_keepdir=0 (PR #10757)

Alexandre Lepretre (Vim Github Repository) wrote: @Matsa59 pushed 1 commit. * af9a9d2 Merge branch 'vim:master' into master In looking over your patch, it looks like the

Re: [vim/vim] [netrw] Fix file move when g:netrw_keepdir=0 (PR #10757)

Alexandre Lepretre (Vim Github Repository) wrote: @Matsa59 pushed 1 commit. * 22bd830 Merge branch 'vim:master' into master — View it on GitHub

Re: how to get old versions of vim

Maxim Kim wrote: On 27/08/2022 07:56, Charles Campbell wrote: So, I thought what I'd like to do is to get vim 9.0 back (with no patches) and see if that worked. Then, if the plugin continues to misbehave, then I'd like to get vim 8.0. Once I have a version of vim where the plugin works

how to get old versions of vim

Hello: I've got a plugin that I wrote years ago that I only just noticed is misbehaving; ie. it used to work properly but it no longer does. So, I thought what I'd like to do is to get vim 9.0 back (with no patches) and see if that worked. Then, if the plugin continues to misbehave, then

Re: RV: Fix netrw plugin issue using powershell #10931

miguel wrote: References PR: https://github.com/vim/vim/pull/10931 Thanks for your time  Thank you for the improvement! As you may surmise, I don't use powershell, so its really helpful to have folks who use something give feedback. Currently, netrw v172f is on my website

Re: [vim/vim] netrw opens empty buffer instead of actual file contents (#3276)

drakuno (Vim Github Repository) wrote: Hello. I am having this problem. I followed the |h: netrw-debug| steps. You can find the results here: https://gist.github.com/drakuno/978224d0250ab3660c7ad83be4fcbbd7 An issue while debugging was that upon running |vim -u netrw.vimrc --noplugins -i

Re: syntax/vim.vim - support python << trim

Ben Jackson wrote: Thanks, Bram, will do. I just looked over your patch. Why is it necessary? syntax/vim.vim, without it, already handles py3

Re: [vim/vim] zipfile opens an empty buffer after 8.2.3468 (#8974)

Christian Brabandt (Vim Github Repository) wrote: Okay, so how about the following patch. It checks, whether the filename starts with something that looks like a protocol specifier like |http:/| or in this case |zipfile:/| and in that case does not prepend the current directory to it

Re: [vim/vim] zipfile opens an empty buffer after 8.2.3468 (#8974)

Christian Brabandt (Vim Github Repository) wrote: Hm, the tar filetype come from this line in the plugin: https://github.com/vim/vim/blob/master/runtime/autoload/zip.vim#L118 I don't think this is correct. For the other issue, let me have a quick look Thanks! I'd completely forgotten

Re: [vim/vim] runtime/syntax/vim: Fix vimOper ordinal. (#7966)

Bram Moolenaar wrote: Tsuyoshi CHO (Vim Github Repository) wrote: @tsuyoshicho pushed 1 commit. * 419101f vim operator syntax fix Hello, Tsuyoshi: Unfortunately,

Re: [vim/vim] runtime/syntax/vim: Fix vimOper ordinal. (#7966)

Tsuyoshi CHO (Vim Github Repository) wrote: @tsuyoshicho pushed 1 commit. * 419101f vim operator syntax fix Hello, Tsuyoshi: Unfortunately, github is telling me that it

syntax/vim.vim question -- should vim's heredocs be highlighted with comment support?

Hello, Its been brought to my attention (thanks, Naruhiko Nishino) that vim's heredoc's syntax highlighting may not need to support commenting, either old-style or vim9 style. Some of the examples show vimL use, where comment support is nice, but other examples are just plain text. I'm

after updating vim to 8.3.3132, getting seven error messages (E1208)

Hello: Error detected while processing /home/cec/.vim/plugin/AsNeededPlugin.vim: line   61: E1208: -complete used without -nargsline I certainly didn't get these before, nor do I know what -nargsline is. The relevant line: com! -nargs=0 -complete=command MakeANtags    call

are lambdas being used for legacy?

Hello: I'm not knowingly using lambdas. I'm trying to debug some netrw code and I keep ending up with the following error: ." is a directory Error detected while processing VimEnter Autocommands for "*"..function 72_VimEnter[15]..1[1]..72_LocalBrowse[32]..netrw#LocalBrowseCheck: line   26:

Re: Insert non-rectangular selection

Maxim Kim wrote: like a `zp` command, that does not add any trailing spaces. Btw if you paste at the end of the `;text` no trailing spaces would be added. Well, that messes with my own zp and zP maps, but no problem. I've also overridden p and P with them, so I can just eliminate zp

Re: [vim/vim] doc: ":tc" is no longer the abbreviation of ":tcl" (#8258)

lacygoill (Vim Github Repository) wrote: did you detect this by luck or do you have an automated way of finding whether the doc is inconsistent with the actual command being run? I guess it's a bit of both (luck + automated way). I'm rewriting the default Vim syntax plugin to get

vim help and netrw

Hello: I have a tester for netrw which I was using to try to verify netrw before it gets sent out. Its failing at an odd place; it issues a key to obtain help. When I run the test with just the one script, the help shows 18 lines, a separator, 3 lines from the file, and a separator; the

problem with a command that I didn't used to have

Hello: A heads up... I have my own script which runs latex called s:MakeLatex(early) . Note that it takes one parameter. However, recently, I run the command once and it works; the second time I get a "E118: Too many arguments for function: 127 MakeLatex . I set up a command "com! LatexFun

Re: [vim/vim] Multi-line Comment Indenting With C -- incorrect initial spacing (#8118)

Bram Moolenaar (Vim Github Repository) wrote: Closed #8118 . Thank you, Bram! I've been suffering with that problem for years -- and it was just an option I set up years ago. I've now set that parameter to 200... Chip Campbell -- -- You received

Re: [vim/vim] Multi-line Comment Indenting With C -- incorrect initial spacing (#8118)

cecamp (Vim Github Repository) wrote: *Describe the bug* Normally, a multi-line comment in C will show a new "*" at the correct indentation every time a carriage return is entered. However, that is not the case with the attached example file. Instead, extra (unwanted) spaces are prepended

Re: syntax/ratpoison.vim update

Bram Moolenaar wrote: Magnus Woldrich wrote: Attached is an updated ratpoison.vim syntax file. It's also here[0]. [0] https://github.com/trapd00r/vim-syntax-ratpoison/commit/873a2e465a314d5017a56c90d15f7bef18dbc43c The patch doesn't apply to what I have, thus I got the file from github.

Re: [vim] vim creates large swp files

Kirill Ryzhkov wrote: Hi Vim developers! I use vim on Linux all the time and found a problem with creating just huge swp files that can take up all the hard disk space. If you open vim and copy a large text that can cause the linux console to hang and then you force close the console, after a

Re: [vim/vim] netrw's "gx" functionality doesn't open URLs anymore in macOS (#4738)

K.Takata (Vim Github Repository) wrote: It seems that my patch has been (partly) included in the prerelease version: http://www.drchip.org/astronaut/vim/#NETRW. If @cecamp thinks it is ready for releasing, he will send the files to Bram. But he doesn't think it is

Re: [vim/vim] Force help to open in current window. (#7534)

Pavol Juhas wrote: I think this can work without opening/closing help, the trick is to set buftype=help. Also :view is preferable so that the main help file opens as read-only. $ vim :view `=` :setlocal buftype=help :help grail As a command, and using a modified method:   com! -nargs=+ HE

Re: [vim/vim] netrw is slow over ssh (#7259)

Christian Brabandt wrote: On Fr, 18 Dez 2020, Charles Campbell wrote: Christian Brabandt (Vim Github Repository) wrote: As far as the clipboard goes: it copies the clipboard into a local variable, and only if the clipboard value has changed during the course of netrw's

Re: [vim/vim] netrw is slow over ssh (#7259)

Christian Brabandt (Vim Github Repository) wrote: As far as the clipboard goes: it copies the clipboard into a local variable, and only if the clipboard value has changed during the course of netrw's operation will netrw restore the clipboard value (thus avoiding having netrw

Re: How to create a syntax keyword at runtime?

Ron Aaron wrote: I explained exactly what I mean in the original post. Yes, of course I'm talking about a specific file type, but the specific type is unimportant since it's something I'm creating and not something in the

Re: How to create a syntax keyword at runtime?

Ron Aaron wrote: Is this possible w/ vim's syntax highlighting? On Wednesday, December 9, 2020 at 10:56:35 AM UTC+2 Ron Aaron wrote: Hi all - I want to have a keyword (user-defined function) highlighted by my syntax file. The code looks like this:     :  foo  blah blah ;

Re: Patch 8.2.2068

Bram Moolenaar wrote: Patch 8.2.2068 Problem:Transparent syntax item uses start/end of containing region. Solution: Do not change the startpos and endpos of a transparent region to that of its containing region. (Adrian Ghizaru, closes #7349,

unwanted escape sequences

Hello! Recently, as in the last year or so, I've been getting unwanted escape sequences; I've tracked down the issue to a simple operation: vim -u NONE -U NONE :q and I get left with >4;m>4;2m.  My system uses linux (Scientific Linux 7.9),

Re: [vim/vim] netrw: Fix gx command (#7188)

Charles Campbell wrote: James McCoy wrote: On Thu, Oct 22, 2020, 21:39 Charles Campbell <mailto:campb...@drchip.org>> wrote:     I confess that I'm not a git master.  It'd be a help if you could     send     me a patch instead of a commit which I don't use If you append ".d

Re: [vim/vim] netrw: Fix gx command (#7188)

James McCoy wrote: On Thu, Oct 22, 2020, 21:39 Charles Campbell <mailto:campb...@drchip.org>> wrote: I confess that I'm not a git master.  It'd be a help if you could send me a patch instead of a commit which I don't use If you append ".diff" to a pull request

Re: [vim/vim] netrw: Fix gx command (#7188)

K.Takata (Vim Github Repository) wrote: Fix #4738 . Since Netrw v165, the gx command had been broken at least on macOS and MS-Windows. The platform-specific open commands support to handle a remote URL directly, however, Netrw downloaded a file first.

Re: [vim/vim] netrw's "gx" functionality doesn't open URLs anymore in macOS (#4738)

K.Takata (Vim Github Repository) wrote: I created PR #7188 . @cecamp Please check this. I no longer have access to a Mac; I thus depend on someone to forward a patch to me which addresses the problem. Chip Campbell -- -- You

Re: [patch] fixed typos in doc of vim-8.2.1673

Dominique Pellé wrote: Hi Attached patch fixes typos in documentation of Vim-8.2.1673. I don't know, I rather like the idea of a re-tuned dictionary!  Like a guitar... Chip Campbell -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text

A latex issue involving \text

Hello: For some reason I just cannot find the email that involved the following problem: Correct syntax $math$ here $\text{(20, 25]}$ Wrong syntax here... Anyway, this is a problem with unwanted checking for matched delimiters.  I've now provided more selectivity for matching

matchit problems

Hello, Christian: I see that you've picked up maintaining the matchit plugin.  I've been having problems with it recently -- problems that I didn't used to have. * I used to be able to use the % key, in vimscript, to jump between if .. elseif ..endif * I used to be able to bypass {{{3 in

Re: [vim/vim] Wrong syntax coloring (#6331)

Christian Brabandt wrote: On Do, 25 Jun 2020, Charles Campbell wrote: I think it is not about matchit itself, it was just an example. The thing was when using a plugin manager like vim-plug and you want to enable the matchit plugin, you use: Plug 'k-takata/matchit.vim' in your vimrc

Re: [vim/vim] Wrong syntax coloring (#6331)

Charles Campbell wrote: K.Takata (Vim Github Repository) wrote: I can confirm that: |'k| is shown as vimMark. |-| is shown as vimOper. |.| is shown as vimOper. |vim| is shown as vimCommand. @cecamp <https://github.com/cecamp> Could you check this? BTW, |k-takata/matchit.vim| is now

Re: [vim/vim] Wrong syntax coloring (#6331)

K.Takata (Vim Github Repository) wrote: I can confirm that: |'k| is shown as vimMark. |-| is shown as vimOper. |.| is shown as vimOper. |vim| is shown as vimCommand. @cecamp Could you check this? BTW, |k-takata/matchit.vim| is now merged into |chrisbra/matchit|,

Re: [vim/vim] :help netrw-browse-maps show wrong mapping for netrw-c (#6266)

DiegoRenner (Vim Github Repository) wrote: *Describe the bug* In the output of :help netrw-browse-maps the keybinding to change the diretory to the current one is declared to be c. In the output of :help netrw-c however it is said that the keybinding for this is now cd which seems to be

Re: [vim/vim] Distinguish between zg and zG, and zw and zW (#6140)

Christian Brabandt (Vim Github Repository) wrote: How about: diff --git a/runtime/doc/index.txt b/runtime/doc/index.txt index 78d557f51..dded70d32 100644 --- a/runtime/doc/index.txt +++ b/runtime/doc/index.txt @@ -828,7 +828,7 @@ tag char note action in Normal mode ~

Fwd: Vim syntax (variables)

Hello: I don't know how my old (as in no longer active) email address remained in syntax/vim.vim, because I updated all of the syntax files with my new address. I just sent an updated syntax/vim.vim to Bram  with the correct email address. Just look at any of the other syntax files I maintain

Re: git pull problems from vim repository

Tony Mechelynck wrote: On Sun, May 17, 2020 at 9:40 PM Charles Campbell wrote: Hello: I seem to have a problem doing git pull: fatal: Not a git repository (or any parent up to mount point /home) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set

git pull problems from vim repository

Hello: I seem to have a problem doing git pull:     fatal: Not a git repository (or any parent up to mount point /home)     Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). Fortunately git clone https://github.com/vim/vim.git works, but that's a lot more work.

Re: [vim/vim] In bash syntax you can't escape a backquote in a double-quoted string. (#5991)

John Little wrote: This is a regression, the syntax/sh.vim from 2019-06-16 does not show this problem. The maintainer of this syntax script has his own version numbering, and if you want to report problems he usually will first ask that you try the latest script from his web site, which is

Re: On Windows - other tabs close when netrw explore navigates to a directory

More information would be helpful:     * what/which binary is exhibiting the problem?     * What is its version (:version)?     * If you compiled it, how did you compile it (which compile-time options, which compiler)?     * Is it for native Windows (usually gvim in that case), cygwin (vim or

Fwd: Re: [patch] broken link pi_logipat.txt in runtime/doc/help.txt

Forwarded Message From: 12 2016 <> X-Mozilla-Status: 0001 X-Mozilla-Status2: 0080 X-Mozilla-Keys: Subject:Re: [patch] broken link pi_logipat.txt in runtime/doc/help.txt To: vim_dev@googlegroups.com References:

Re: [vim/vim] VIM highlights valid POSIX shell syntax as errorneous (#1147)

Andrew Shadura wrote: > > @chrisbra , why have you closed it? It is > documented, yet it is wrong, and has to be changed. > > "No need to quote RFCs or market penetration statistics". Clearly you are a posix user; there are also many bash users. In fact, there are

Re: [vim] Vim cryptmethod uses SHA-256 for password-based key derivation (#639)

Bram Moolenaar wrote: > My favorite example is when I have some text that I don't want my > neighbor to read. Any encryption that Vim provides works for that. > Also keep in mind that, no matter how strong your encryption is, there > is always a weak point. Rembember key loggers? There never ever

Re: [PATCH 0/3] syntax: sh: heredoc fixes

Felipe Contreras wrote: > Hello? > > Why hasn't this been fixed? > I don't read every message on the list, plus I've been busy lately. As Nikolay Pavlov mentions, emailing me directly is the best way to get things into the syntax files I maintain. I suggest that you try the latest version of

Re: [vim/vim] propose vim as manpager that syntax highlights and follows symlinks (#491)

Nick James wrote: > > If I invoke vim without a file |vim| then type |:Man vim| I get |E492: > Not an editor command: Man vim|. I /think/ this is expected. > > If I invoke vim without a file |vim| then type |:set filetype=man| > followed by |:Man vim| it opens correctly. On my system (RHEL 6.5) >

Re: [vim/vim] propose vim as manpager that syntax highlights and follows symlinks (#491)

Charles E Campbell wrote: > Murukesh Mohanan wrote: >> Typically man pages have bold and underlines displayed using |x\bx| >> and |_\bx|, |\b| being the backspace and |x| the letter in question >> (Thomas Dickey talks about this in this Unix & Linux post >>

Re: Patch 7.4.1770

Bram Moolenaar wrote: > Charles Campbell wrote: > >> Bram Moolenaar wrote: >>> Patch 7.4.1770 >>> Problem:Cannot use true color in the terminal. >>> Solution: Add the 'guicolors' option. (Nikolai Pavlov) >>> Files: runtime/doc/options.tx

Re: Patch 7.4.1770

Bram Moolenaar wrote: > Patch 7.4.1770 > Problem:Cannot use true color in the terminal. > Solution: Add the 'guicolors' option. (Nikolai Pavlov) > Files: runtime/doc/options.txt, runtime/doc/term.txt, > runtime/doc/various.txt, src/auto/configure, src/config.h.in, >

Re: [vim/vim] sh syntax hightlight breaks on "${VAR/FOO/\\[}" (#759)

Alexander Meshcheryakov wrote: > "${VAR/FOO/\\[}" > > is a bashism to substitute |'FOO'| in |$VAR| with |'\['| > vim fails to notice trailing double quote and the of a script becomes > highlighted as doublequoted. Demo script to check highlighting: > > #!/bin/bash > VAR1=FOOBAR >

Re: Channel & job design

Charles Campbell wrote: > Bram Moolenaar wrote: >> Lcd wrote: >> >> There are also UNIX domain sockets (a.k.a. named pipes), which you get >> essentially for free once you have the code for INET sockets. They are >> as efficient as (unnamed) pipes. The code is al

Re: Channel & job design

Bram Moolenaar wrote: > Lcd wrote: > > There are also UNIX domain sockets (a.k.a. named pipes), which you get > essentially for free once you have the code for INET sockets. They are > as efficient as (unnamed) pipes. The code is already there, but it's > mutually exclusive with INET sockets. I

Re: [bug] netrw remote delete

Carlos Pita wrote: > Hi all, > > I'm getting this error message when trying to delete (pressing D) a file on a > remote directory: > > Error detected while processing function > 28_NetrwRemoteRm[32]..28_NetrwRemoteRmFile: > line 60: > E488: Trailing characters: else if ret != 0 > > Doing

warnings and a hang

Hello: I use ./configure --with-features=huge --enable-gui=gtk2 --enable-perlinterp --enable-pythoninterp --enable-rubyinterp --enable-cscope for configuring. When I attempt to compile: (using gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)) if_perl.xs|53 warning| expected

Re: [vim] sh.vim incorrectly highlighting if/fi (#636)

mattn wrote: > > Could you please try below? > > |$ vim -u NONE -N your.sh :syntax on ... move cursor into `--install` > above ... :echo synIDattr(synID(line("."), col("."), 1), "name") | > > I get shOption. > > I get shOption. That's what --install is supposed to be highlighted as. More fully:

Re: [vim] Netrw: special directory names causes Vim to display directories as if they were empty [Bug] (#657)

Jelly wrote: > > I discovered this whilst trying to use Vim's Netrw as my file manager > (for more generic use). > Me, including two other experienced users have successfully reproduced > what seems to be a bug. > > *Reproducing the bug:* > > |$ mkdir "Foo [Bar]" && cd $_ $ touch a b c $ vim . | >

Re: [vim] sh.vim incorrectly highlighting if/fi (#636)

mattn wrote: > > try following on cursor at |--install|. > > |echo synIDattr(synID(line("."), col("."), 1), "name") | > > what do you get? > > Using hilinks.vim, which gives rather more information, and with the cursor on --install: SynStack: shOption

Re: Why "loadplugin" when there's already "loadplugins"?

Bram Moolenaar wrote: > Right, the name is not ideal, but I could not think of a better one. I > would also use "bundle" instead of package or pack, but plugin > managers already use it and there could be a conflict. I hope that the > new mechanism doesn't break existing behavior. Nikolay, you had

Re: [vim] sh.vim incorrectly highlighting if/fi (#636)

Josh Reichardt wrote: > > OS: |OS X 10.11.3| > vim version: |7.4 (2013 Aug 10, compiled Feb 11 2016 11:34:55)| > Info for filetype: |sh| > > To reproduce: > > |#!/usr/bin/env bash if ! which "xcode-select" > /dev/null; then echo > "No xcode" else xcode-select --install fi | > > The select in

Re: loaded_LogiPat

mattn wrote: >> The problem is that the cases of the variables are different. So there's >> no need to change the value "v3" to 1. >> It seems that Dr. Chip's guards are based on the filenames. So using >> "loaded_logiPat" might be consistent. > Yes, I know. So I said: > > You may want to add

Re: Patch 7.4.1166

Bram Moolenaar wrote: > Patch 7.4.1166 > Problem:Can't encode a Funcref into JSON. jsonencode() doesn't handle the > same list or dict twice properly. (Nikolay Pavlov) > Solution: Give an error. Reset copyID when the list or dict is finished. > Files: src/json.c,

Patch 866 Problem

Hello! Bram asked me to send you my small script which evokes a problem I'm having with Patch #866. To use it: vim -u NONE Hang.vim :set nocp :so % :Hang What happens: Hang sets up a remote gvim server which also sources Hang.vim. The server then gets told to call Hang#ToClient() which uses

Re: Patch 7.4.960

Bram Moolenaar wrote: > Patch 7.4.960 > Problem:Detecting every version of nmake is clumsy. > Solution: Use a tiny C program to get the version of _MSC_VER. (Ken Takata) > Files: src/Make_mvc.mak > Hi! This patch isn't on ftp.home.vim.org yet. Chip Campbell -- -- You received this

Re: [vim] comments inside parentheses mess up the syntax coloring of shell script (#487)

Christian Brabandt wrote: > > Please discuss this with the maintainer of the current indentation > file. See Contributing.md > > > I see no problems. Try the latest

Re: proposed patch: Make syntax highlighting independent of 'iskeyword' setting

Christian Brabandt wrote: > That is true with many patches however. It works only well, if > contributors do use it. And a lot of syntax files need to be > maintained, if only because the language evolves within times. Best, > Christian Also because suggested syntax changes are occasionally

Re: [vim] Netrw doesn't enter the directory symbolic link (#445)

yurivict wrote: > > When I view the directory (:new .), select symbolic link representing > another directory, and hit Enter, vim still stays the original directory. > > vim-7.4.891 on FreeBSD-10.2 > Hello! I'm afraid that I don't see this problem. (I use vim v7.4.891 with Scientific Linux 6.7)

Re: Missing syntax highlighting in sh syntax inside the braces

Yuri wrote: > I am seeing that '=' and '&&' elements aren't highlighted in this > example. > However, when when the braces are removed it highlights ok. > > filetype=sh, is_posix=1 > FreeBSD > > Yuri > > > --- problem testcase: = and && aren't highlighted! --- > #!/bin/sh > > myfunc() { > ([

Re: Issue 364 in vim: sh syntax highlight breaks on "'\$#'": everything after becomes shDoubleQuote

v...@googlecode.com wrote: > a=b > echo "'\$#'" > c=d Hello! Thank you for your feedback, and sorry it took awhile to get to it. Please try the latest syntax/sh.vim from my website to address this issue: http://www.drchip.org/astronaut/vim/index.html#SYNTAX_SH Regards, Chip Campbell -- --

Re: netrw on windows+shellslash

mattn wrote: > Hi. > > I wrote a patch to enable http/ftp/webdav access with netrw on > windows+shellslash. I'm using vim but not use cygwin or msys2. However, then > editing http file on vim, URL is displayed as: > > http:\\example.com\foo.html > > So I want to use shellslash on windows too.

Re: [vim] Error detected while processing function 113_NetrwBrowseChgDir: (#442)

Aaron Goshine wrote: > > fchdir() to previous dir > |Error detected while processing function > 19_LocalBrowse[30]..netrw#LocalBrowseCheck[21]..28_NetrwBrowse[233]..28_PerformListing[220]..28_NetrwOptionRestore: > line 86: > | > > It'd help me to help you if you used the latest release of netrw

Re: netrw on windows+shellslash

Nikolay Pavlov wrote: > 2015-10-08 20:44 GMT+03:00 Charles Campbell <charles.e.campb...@nasa.gov>: >> mattn wrote: >>> Hi. >>> >>> I wrote a patch to enable http/ftp/webdav access with netrw on >>> windows+shellslash. I'm using vim but not use cy

Re: Patch 7.4.855

Charles Campbell wrote: > Bram Moolenaar wrote: >> Patch 7.4.855 >> Problem:GTK: font glitches for combining characters >> Solution: Use pango_shape_full() instead of pango_shape(). (luchr, PR #393) >> Files: src/gui_gtk_x11.c >> >> >> *** .

Re: VIM now crashes when opening large file:

Ben Fritz wrote: > 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). >> >> here was the last crash message details: >> Problem signature: >> Problem Event Name:APPCRASH >> Application Name: gvim.exe >>

Re: Patch 7.4.855

Christian Brabandt wrote: > Hi Charles! > > On Mi, 09 Sep 2015, Charles Campbell wrote: > >> I'll further mention that I can no longer compile vim on my linux >> workstation because of the undefined reference. I see where use of it >> is protected by a #ifdef

Re: Patch 7.4.855

Bram Moolenaar wrote: > Patch 7.4.855 > Problem:GTK: font glitches for combining characters > Solution: Use pango_shape_full() instead of pango_shape(). (luchr, PR #393) > Files: src/gui_gtk_x11.c > > > *** ../vim-7.4.854/src/gui_gtk_x11.c 2015-06-09 19:14:18.773373964 +0200 > ---

small problem with eval.c

Hello! I just upgraded from patch level 841 to 854 -- and got two warnings. I've provided a trivial patch for the eval.c one and, as the misc * eval.c|4412 error| 'i' undeclared (first use in this function) * misc2.c|6265 warning| ignoring return value of 'fwrite', declared with attribute

another tooltip issue

Hello! When I have a tooltip window appear, and then change workspaces (via ctrl-alt-arrow under gtk/linux), the tooltip window appears in the new workspace. Moving the mouse about doesn't affect it. Regards, Chip Campbell -- -- You received this message from the "vim_dev" maillist. Do not

Re: Patch 7.4.840

Bram Moolenaar wrote: > Patch 7.4.840 (after 7.4.829) > Problem:Tooltip window stays open. > Solution: Send a WM_CLOSE message. (Jurgen Kramer) > Files: src/gui_w32.c > > > *** ../vim-7.4.839/src/gui_w32.c 2015-08-25 12:21:23.583957205 +0200 > --- src/gui_w32.c 2015-08-26

Re: Question regarding :normal

Quinn Strahl wrote: On Wednesday, 26 August 2015 01:31:34 UTC-4, Justin M. Keyes wrote: On Tue, Aug 25, 2015 at 10:00 PM, Quinn Strahl qstr...@gmail.com wrote: A difference in behaviour between :g and :rangenormal recently frustrated me, and I wonder if it's up for debate: :g does a pass

Re: Gnuplot Syntax Patch

Josh Wainwright wrote: Hi Christian, Well, would you volunteer to maintain this syntax file? I haven't exactly volunteered, but am more than happy to do so. Is it back to this list that I send the updated file? No, send your patches directly to Bram Moolenaar. Tell him the situation of

Re: minor bug in the LogiPat plugin for Vim

LCD 47 wrote: This has been mentioned on StackOverflow: LogiPat sets g:loaded_LogiPat, but checks for loaded_logipat: http://stackoverflow.com/a/31695784 Obvious fix below. Best regards, /lcd diff --git a/runtime/plugin/logiPat.vim b/runtime/plugin/logiPat.vim

Re: Proposal: fixing Todo highlighting chaos

Jean-François Bignolles wrote: Hello, Using different languages, I remarked that the Todo system (highlighting of special words inside comments) was currently a bit chaotic: some keywords are highlighted for one syntax, but not for an another one. (I won't talk here of syntax files which

Re: expand(%) and utf-8 characters in directory names

Christian Brabandt wrote: Am 2015-04-20 18:28, schrieb Charles Campbell: I've attached a small tarball illustrating the problem I'm having with expand(). gunzip jose.tar.gz tar xf jose.tar cd josé vi junk.vim :so % :echo x[4] :echo y[4] With the first echo, you'll see (using utf-8

Re: patch to allow locking/unlocking the jump list

Carlo Baldassi wrote: Yes, I had that thought as well. However, as also clearly stated in the documentation of lockmarks, the major drawbacks of this model are 1) not adjusting for line insertions / deletions 2) the possibility of making the command you're calling non-functional, it that

Re: patch to allow locking/unlocking the jump list

Carlo Baldassi wrote: Hello! I'm wondering about how the patch(es) work -- is it a saverestore or is it a prevent-any-modification? I'm in favor of saverestore; prevent-any-modification is certainly going to cause problems. Hi! The lockjumps patch (filename: lkjcmd_patch.txt) does a

Re: Wrong dollar sign red color highlighting in shell scripts

Yuri wrote: On 03/21/2015 02:08, John Little wrote: 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. In BSD Almquist shell,

Re: runtime: zsh syntax: include Zsh options

Nikolai Weibull wrote: On Sun, May 10, 2015 at 6:47 PM, Daniel Hahler google-groups+2...@thequod.de wrote: I think it would be great if the Zsh options would be in the zsh syntax file, which would also allow for them to be used through syntaxcomplete#Complete. I am attaching a patch for

Re: expand(%) and utf-8 characters in directory names

Charles Campbell wrote: Christian Brabandt wrote: Hi Charles! On Fr, 27 Mär 2015, Charles Campbell wrote: Bram Moolenaar wrote: Charles Campbell wrote: I tried a directory named josé and found that netrw wasn't handling it well. One of the reasons is expand(%), which is used to get

Re: Issue 321 in vim: syntax/tex.vim does not track braces inside \ensuremath{} blocks

v...@googlecode.com wrote: Comment #4 on issue 321 by ewtoo...@gmail.com: syntax/tex.vim does not track braces inside \ensuremath{} blocks https://code.google.com/p/vim/issues/detail?id=321 I just checked again, and v.84 isn't working. I'd forgotten to prevent loading of my .vimrc last time

Re: Preparations for moving to github

Ben Fritz wrote: On Friday, March 27, 2015 at 4:06:47 PM UTC-5, Bruno Sutic wrote: - lastly, it has been mentioned a couple times vim plugin community is already on github. The objective statement that proves this: github currently has 42,636 vim related repositories, bitbucket has only 1652

Re: expand(%) and utf-8 characters in directory names

Christian Brabandt wrote: Hi Charles! On Fr, 27 Mär 2015, Charles Campbell wrote: Bram Moolenaar wrote: Charles Campbell wrote: I tried a directory named josé and found that netrw wasn't handling it well. One of the reasons is expand(%), which is used to get the full path. However

Re: expand(%) and utf-8 characters in directory names

Bram Moolenaar wrote: Charles Campbell wrote: I tried a directory named josé and found that netrw wasn't handling it well. One of the reasons is expand(%), which is used to get the full path. However, when in that directory, expand(%) shows /home/cec/joee9 instead of the desired /home/cec

expand(%) and utf-8 characters in directory names

Hello: I tried a directory named josé and found that netrw wasn't handling it well. One of the reasons is expand(%), which is used to get the full path. However, when in that directory, expand(%) shows /home/cec/joee9 instead of the desired /home/cec/josé . Do I need to program around this or

Re: broken sytanx of vim.vim

mattn wrote: let g:foo = 1 The SynID of foo is not vimVar. Currently, it's vimIsCommand. IFAIK, it was vimVar in few month ago. I'm thinking vimIsCommand is too generally pattern. syn match vimIsCommand\\h\w*\ contains=vimCommand syn match vimVar \[bwglsav]:\K\k*\

  1   2   3   4   5   >