Re: Patch 8.2.4510

> After requiring to use ":var" and disallow ":va", to make Vim9 scripts > more readable, I was wondering if we should do this for more commands. > Especially using "en" instead of "endif" makes a script harder to > understand. So why not do it for all the flow commands? > > Let me know if

Re: Vim9 script feature-complete

On Friday, January 7, 2022 at 2:01:49 PM UTC-6 Bram Moolenaar wrote: > > Manuel Ortega wrote: > > > I very much hope that one thing will be changed. Currently '#' only > starts > > a comment when it's followed by a space, if I understand correctly. > Please >

Re: Vim9 script feature-complete

I very much hope that one thing will be changed. Currently '#' only starts a comment when it's followed by a space, if I understand correctly. Please make it instead behave like almost every other language that uses '#' as a comment character, and *don't* require that it be followed by a

Re: gui segfault macos-10.11.6 vim-8.1.1566 openmotif-2.3.8

On Tuesday, June 18, 2019 at 4:50:09 AM UTC-5, raf wrote: > hi, > > macosx-10.11.6 > vim-8.1.1566 > XQuartz-2.7.11 > openmotif-2.3.8 (via macports-2.5.4) > > i just tried to upgrade vim on macos for the first time in a year > (from 8.1.10 to 8.1.1566) and it segfaults if i run "vim -g" or >

Re: Window-local and Tab-local previous directories?

On Tuesday, May 14, 2019 at 12:17:06 PM UTC-4, yega...@gmail.com wrote: > Hi, > > On Sat, May 11, 2019 at 10:12 AM Manuel Ortega wrote: > > > > On Friday, May 10, 2019 at 5:20:08 PM UTC-4, Bram Moolenaar wrote: > > > > > I think that's the best way we pro

Re: Window-local and Tab-local previous directories?

On Friday, May 10, 2019 at 5:20:08 PM UTC-4, Bram Moolenaar wrote: > I think that's the best way we provide this functionality. But I like > to hear from others. I think this is adding complexity, a maintenance burden, and yet another corner for corner-cases to hide in, all for the sake of a

Re: Patchlevel 8.1.698 broke clearing of vim status line when switching between tabs

On Thu, Apr 18, 2019 at 11:42 AM wrote: > On Thursday, April 18, 2019 at 5:21:50 PM UTC+2, Manuel Ortega wrote: > > Yes: all you need to do is use an autocommand event like say TabEnter > or TabLeave to do e.g. ':silent redraw` whenever a tab is entered/left. > > That works, t

Re: Patchlevel 8.1.698 broke clearing of vim status line when switching between tabs

On Thu, Apr 18, 2019 at 6:16 AM wrote: > Hi, > > I'm the user who originally reported this. > > On Thursday, April 18, 2019 at 8:43:31 AM UTC+2, Christian Brabandt wrote: > > Yes as mentioned before, it might be unexpected, that the last output > > from a command or a plugin will be erased just

Re: Proposal for text property feature

Unfortunately without a simple example or two, I don't understand this at all. (I not only don't see what it does, I also don't see why this would benefit anything.) -Manny -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are

Re: Problem with Vim 8.1.332 and 8.1.347 viewing .tgz files

On Fri, Sep 7, 2018 at 4:23 PM Bram Moolenaar wrote: > > 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 > >

Re: Scrolling in Vim

On Sun, Aug 26, 2018 at 10:29 AM Jason Franklin < jrfrank...@georgiasouthern.edu> wrote: > Normally, scrolling up in vim (i.e., to view the last parts of a file) > will allow you to scroll past > the last line of the file. I'd like for Vim to stop at the end of the > file and not let me go

Re: Using terminal window for external commands in the GUI

On Sun, Mar 18, 2018 at 5:04 PM, Kazunobu Kuriyama < kazunobu.kuriy...@gmail.com> wrote: > 2018-03-19 5:25 GMT+09:00 Manuel Ortega <mannyvim...@gmail.com>: > >> >> >> Finally, another reason to not put "!" in by default just yet is >> that

Re: Using terminal window for external commands in the GUI

On Sun, Mar 18, 2018 at 5:04 PM, Kazunobu Kuriyama < kazunobu.kuriy...@gmail.com> wrote: > 2018-03-19 5:25 GMT+09:00 Manuel Ortega <mannyvim...@gmail.com>: > >> On Sun, Mar 18, 2018 at 4:10 PM, Kazunobu Kuriyama < >> kazunobu.kuriy...@gmail.com> wrote: &

Re: Using terminal window for external commands in the GUI

On Sun, Mar 18, 2018 at 4:10 PM, Kazunobu Kuriyama < kazunobu.kuriy...@gmail.com> wrote: > 2018-03-19 4:26 GMT+09:00 Bram Moolenaar : > >> >> Until recently, the GUI used a "dumb" terminal for external commands. >> With patch 8.0.1616 it is now possible to run an external

Re: Moving away from SourceForge

> We're currently responding to a DDOS that's unrelated to the recent issues. I > also don't even own a suit. It's one thing after another. The fact that the later thing is unrelated to the previous thing is no comfort, when there keeps on being later things. In fact, it makes it even worse.

Re: Moving away from SourceForge

The vim website has been unreachable again, all morning. I can't look in the scripts section for a syntax file I need. I was looking forward to a change of provider. Is Vim really staying with sourceforge just because one of their suits said "pretty please"? -Manny -- -- You received this

8.0.1270 breaks tests on macOS

>From test_ins_complete.vim: Found errors in Test_ins_complete(): function RunTheTest[34]..Test_ins_complete line 58: Expected 'Xtest11.one' but got 'xterm_ramp.vim' TEST FAILURE make[2]: *** [report] Error 1 make[1]: *** [scripttests] Error 2 make: *** [test] Error 2 -Manny -- -- You received

Re: More test failures on macOS

On Saturday, November 4, 2017 at 5:24:05 PM UTC-4, Manuel Ortega wrote: > I just tried building 8.0.1264 from a fresh git clone.  There are more test > failures on macOS 10.12.6: Bisection reveals that the offending patch is 8.0.1263. -Manny -- -- You received this message from the &q

More test failures on macOS

I just tried building 8.0.1264 from a fresh git clone. There are more test failures on macOS 10.12.6: rom test_undo.vim: Found errors in Test_undo_write(): function RunTheTest[34]..Test_undo_write line 8: Expected ['one one one', 'two', 'two', 'three'] but got ['one one onejust some text',

Re: Security risk of vim swap files

On Tue, Oct 31, 2017 at 6:30 AM, Hanno Böck wrote: > > 3. Ideally they also shouldn't leak currently edited filenames (e.g. > they shouldn't be called /tmp/.test.txt.swp, but more something > like /tmp/.vim_swap.123782173) > But Vim needs to know which swapfile is associated

Re: Tests hang with 8.0.1223

On Thu, Oct 26, 2017 at 4:49 PM, Manuel Ortega <mannyvim...@gmail.com> wrote: > On Thursday, October 26, 2017 at 4:41:13 PM UTC-4, Manuel Ortega wrote: > > On macOS 10.12.6, Vim 8.0.1223 builds but `make test` hangs somewhere in > the middle of running tests.

Re: Tests hang with 8.0.1223

On Thursday, October 26, 2017 at 4:41:13 PM UTC-4, Manuel Ortega wrote: > On macOS 10.12.6, Vim 8.0.1223 builds but `make test` hangs somewhere in the > middle of running tests.  What I see at the hung stage is: > > > "motion.txt" [readonly] 1343 lines, 516

Tests hang with 8.0.1223

On macOS 10.12.6, Vim 8.0.1223 builds but `make test` hangs somewhere in the middle of running tests. What I see at the hung stage is: "motion.txt" [readonly] 1343 lines, 51602 characters Executing Test_vim_did_enter() Executing Test_win_tab_autocmd() "motion.txt" And it stays there until I hit

Re: [patch] use strikethrough for diff filetype

On Tue, Oct 3, 2017 at 10:29 PM, Ben Fritz wrote: > On Monday, October 2, 2017 at 1:05:03 PM UTC-5, Bram Moolenaar wrote: > > Christian wrote: > > > > > Bram, > > > since Vim can now display strikethrough attributes (in the gui), let's > > > make a bit more use of it. >

Re: No rule to make terminal.c

On Tuesday, September 19, 2017 at 6:40:55 PM UTC-4, Tony Mechelynck wrote: > After applying patches 1128-1129, and the runtime files update between > them, both Tiny and Huge builds halt as follows (shown here for Tiny): > > gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall >

Re: Removing FEAT_WINDOWS

On Sat, Sep 16, 2017 at 10:31 AM, Bram Moolenaar wrote: > > So I'll graduate FEAT_WINDOWS. That removes 626 #ifdefs !!! > According to the docs, once this happens the only thing differentiating "tiny" from "small" will be "+visual". But then those same docs also say of

Re: 8.0.1039 broke setline()

On Mon, Sep 4, 2017 at 3:01 AM, Christian Brabandt <cbli...@256bit.org> wrote: > > On Mo, 04 Sep 2017, Manuel Ortega wrote: > > > 8.0.1039 broke setline(). I know this by bisection. To reproduce: > > > > Make a file, testvimrc, that contains one line: "sou

Re: 8.0.1039 broke setline()

On Monday, September 4, 2017 at 3:01:53 AM UTC-4, Christian Brabandt wrote: > On Mo, 04 Sep 2017, Manuel Ortega wrote: > > > 8.0.1039 broke setline().  I know this by bisection.  To reproduce: > > > > Make a file, testvimrc, that contains one line: "source foo&qu

8.0.1039 broke setline()

8.0.1039 broke setline(). I know this by bisection. To reproduce: Make a file, testvimrc, that contains one line: "source foo". Create the file "foo", and let it contain only the following: call setline(1, "Hello There") To show the bug, do: vim -u testvimrc -u NONE -N Expected behavior,

Re: 8.0.995 still fails tests on macOS

The test failures seem to have been successfully dodged by the workaround in 8.0.1049. Thanks! -Manny -- -- 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

Re: 8.0.995 still fails tests on macOS

On Saturday, September 2, 2017 at 8:54:43 AM UTC-4, Bram Moolenaar wrote: > Manuel Ortega wrote: > > > > > Still failing on macOS: > > > > > > > > From test_terminal.vim: > > > > Found errors in Test_terminal_noblock(): > > > &g

Re: 8.0.995 still fails tests on macOS

On Friday, August 25, 2017 at 6:53:23 PM UTC-4, Manuel Ortega wrote: > Still failing on macOS: > > > From test_terminal.vim: > Found errors in Test_terminal_noblock(): > function RunTheTest[24]..Test_terminal_noblock line 21: Pattern 'done' does >

Re: 8.0.995 still fails tests on macOS

On Saturday, August 26, 2017 at 9:50:18 AM UTC-4, Bram Moolenaar wrote: > Manuel Ortega wrote: > > > Still failing on macOS: > > > > From test_terminal.vim: > > Found errors in Test_terminal_noblock(): > > function RunTheTest[24]..Test_terminal_noblock line 2

Re: 8.0.995 still fails tests on macOS

I've run it a few more times, and strangely, the error emitted to the terminal during the `make test_terminal` changes: Executed 18 tests 1 FAILED: Found errors in Test_terminal_scrape_123(): function RunTheTest[24]..Test_terminal_scrape_123[16]..Check_123 line 7: Expected '1' but got ''

Re: 8.0.995 still fails tests on macOS

On Tuesday, August 29, 2017 at 12:49:33 AM UTC-4, Kazunobu Kuriyama wrote: > 2017-08-29 12:16 GMT+09:00 Manuel Ortega <manny...@gmail.com>: > > > On Saturday, August 26, 2017 at 9:58:28 AM UTC-4, Manuel Ortega wrote: > > > On Sat, Aug 26, 2017 at 9:

Re: 8.0.995 still fails tests on macOS

On Saturday, August 26, 2017 at 9:58:28 AM UTC-4, Manuel Ortega wrote: > On Sat, Aug 26, 2017 at 9:50 AM, Bram Moolenaar wrote: > > > > It is working on my Mac machine.  Can you use ch_logfile() to find out > > what happens? > > > Unfortunately, I don't know

Re: 8.0.995 still fails tests on macOS

On Sat, Aug 26, 2017 at 9:50 AM, Bram Moolenaar <b...@moolenaar.net> wrote: > > Manuel Ortega wrote: > > > Still failing on macOS: > > > > From test_terminal.vim: > > Found errors in Test_terminal_noblock(): > > function RunTheTest[24]..Test_te

8.0.995 still fails tests on macOS

Still failing on macOS: >From test_terminal.vim: Found errors in Test_terminal_noblock(): function RunTheTest[24]..Test_terminal_noblock line 21: Pattern 'done' does not match 'ccecho c' function

Re: Patch 8.0.0827

On Tuesday, August 1, 2017 at 10:58:05 AM UTC-5, Manuel Ortega wrote: > On Tuesday, August 1, 2017 at 10:54:29 AM UTC-5, Mats Bertil Tegner wrote: > > Den tisdag 1 augusti 2017 kl. 15:08:33 UTC+2 skrev Bram Moolenaar: > > > Patch 8.0.0827 > > > Problem:Coverity: cou

Re: Patch 8.0.0827

On Tuesday, August 1, 2017 at 10:54:29 AM UTC-5, Mats Bertil Tegner wrote: > Den tisdag 1 augusti 2017 kl. 15:08:33 UTC+2 skrev Bram Moolenaar: > > Patch 8.0.0827 > > Problem:Coverity: could leak pty file descriptor, theoretically. > > Solution: If channel is NULL, free the file descriptors.

8.0.645 test failures on macOS 10.12.5

On macOS 10.12.5, Vim 8.0.645 builds but the tests fail: >From test_hlsearch.vim: Found errors in Test_hlsearch_hangs(): function RunTheTest[24]..Test_hlsearch_hangs line 12: Expected True but got 0 TEST FAILURE make[2]: *** [report] Error 1 make[1]: *** [scripttests] Error 2 make: *** [test]

Re: [vim/vim] Rectified file detection algorithim of tex flavors (#1754)

On Thu, Jun 8, 2017 at 3:49 PM, Bram Moolenaar wrote: > > JackeJR wrote: > > > The algorithim for parsing % and % switched the detected > > filetypes around. i.e. % detected as plaintex, % detected > > as tex. The fix above corrected the matching. > > I do not remembering

Re: [patch] Clean up Mac code

On Sat, Apr 22, 2017 at 1:14 PM, Kazunobu Kuriyama < kazunobu.kuriy...@gmail.com> wrote: > 2017-04-23 0:02 GMT+09:00 Manuel Ortega <mannyvim...@gmail.com>: > >> On Sat, Apr 22, 2017 at 9:11 AM, Kazunobu Kuriyama < >> kazunobu.kuriy...@gmail.com> wrote: &

Re: [patch] Clean up Mac code

On Sat, Apr 22, 2017 at 1:14 PM, Kazunobu Kuriyama < kazunobu.kuriy...@gmail.com> wrote: > 2017-04-23 0:02 GMT+09:00 Manuel Ortega <mannyvim...@gmail.com>: > >> On Sat, Apr 22, 2017 at 9:11 AM, Kazunobu Kuriyama < >> kazunobu.kuriy...@gmail.com> wrote: &

Re: [patch] Clean up Mac code

On Sat, Apr 22, 2017 at 9:11 AM, Kazunobu Kuriyama < kazunobu.kuriy...@gmail.com> wrote: > 2017-04-21 1:48 GMT+09:00 Bram Moolenaar : > >> >> >> The terms "with darwin" and "without darwin" are very confusing. There >> is no help for "darwin". Cleaning that up sounds like a

Re: Patch 8.0.0570

On Fri, Apr 21, 2017 at 5:00 PM, Bram Moolenaar <b...@moolenaar.net> wrote: > > Manuel Ortega wrote: > > > On Thu, Apr 20, 2017 at 4:32 PM, Bram Moolenaar <b...@moolenaar.net> > wrote: > > > > > > > > Manuel Ortega wrote: > > > >

Re: Patch 8.0.0570

On Fri, Apr 21, 2017 at 4:31 PM, Christian Brabandt wrote: > > We have no influence what is provided on the CI system. Yeah, that was my guess. -Manny -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are

Re: Patch 8.0.0570

On Fri, Apr 21, 2017 at 11:10 AM, James McCoy <james...@jamessan.com> wrote: > On Apr 21, 2017 10:25, "Manuel Ortega" <mannyvim...@gmail.com> wrote: > > On Thursday, April 20, 2017 at 3:05:41 PM UTC-4, Manuel Ortega wrote: > > This patch unfortunately compl

Re: Patch 8.0.0570

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 macOS generally: how the h

Re: Patch 8.0.0570

> Since the patch only contains src/configure.ac, please run 'make autoconf' in > the src directory after applying the patch. That works, thanks. I hope that the need to run 'make autoconf' will go away if this patch gets merged. -Manny -- -- You received this message from the "vim_dev"

Re: Patch 8.0.0570

On Thu, Apr 20, 2017 at 6:12 PM, Manuel Ortega <mannyvim...@gmail.com> wrote: > > Don't know if this helps, but the output of "./configure" includes this > line: > > checking for a thread-safe mkdir -p... ./install-sh -c -d > > While the error message from &

Re: Patch 8.0.0570

On Thu, Apr 20, 2017 at 5:59 PM, Manuel Ortega <mannyvim...@gmail.com> wrote: > On Thu, Apr 20, 2017 at 5:56 PM, Manuel Ortega <mannyvim...@gmail.com> > wrote: > >> On Thu, Apr 20, 2017 at 4:32 PM, Bram Moolenaar <b...@moolenaar.net> >> wrote: >> >&

Re: Patch 8.0.0570

On Thu, Apr 20, 2017 at 5:56 PM, Manuel Ortega <mannyvim...@gmail.com> wrote: > On Thu, Apr 20, 2017 at 4:32 PM, Bram Moolenaar <b...@moolenaar.net> > wrote: > >> >> Manuel Ortega wrote: >> >> > On Thu, Apr 20, 2017 at 3:05 PM,

Re: Patch 8.0.0570

On Thu, Apr 20, 2017 at 4:32 PM, Bram Moolenaar <b...@moolenaar.net> wrote: > > Manuel Ortega wrote: > > > On Thu, Apr 20, 2017 at 3:05 PM, Manuel Ortega <mannyvim...@gmail.com> > > wrote: > > > > > This patch unfortunately complete

Re: Patch 8.0.0570

On Thu, Apr 20, 2017 at 3:05 PM, Manuel Ortega <mannyvim...@gmail.com> wrote: > This patch unfortunately completely wrecks parallel builds on macOS > 10.12.4. > > make -j4 > Starting make in the src directory. > If there are problems, cd to the src directory and

Re: Patch 8.0.0570

This patch unfortunately completely wrecks parallel builds on macOS 10.12.4. make -j4 Starting make in the src directory. If there are problems, cd to the src directory and run make there cd src && /Applications/Xcode.app/Contents/Developer/usr/bin/make first .././install-sh -c -d objects

Re: [patch] Clean up Mac code

On Mon, Apr 17, 2017 at 10:41 AM, Kazunobu Kuriyama < kazunobu.kuriy...@gmail.com> wrote: > 2017-04-17 23:24 GMT+09:00 Manuel Ortega <mannyvim...@gmail.com>: > >> On Mon, Apr 17, 2017 at 5:19 AM, Kazunobu Kuriyama < >> kazunobu.kuriy...@gmail.com> wr

Re: [patch] Clean up Mac code

On Mon, Apr 17, 2017 at 5:19 AM, Kazunobu Kuriyama < kazunobu.kuriy...@gmail.com> wrote: > This is a followup to https://groups.google.com/forum/#!topic/vim_dev/ > 5RFo3q8xvfo where we talked about the feature list items relevant to Mac: > > On macOS, what is known as clipboard in our community

8.0.539 has test failure on macOS 10.12.4

Test results: ALL DONE gcc -c -I. -Iproto -DHAVE_CONFIG_H -DMACOS_X_UNIX -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o objects/json_test.o json_test.c In file included from json_test.c:19: ./main.c:1021:12: error: use of undeclared identifier 'params' return params.not_a_term;

Re: [patch] Some improvements for the docs

On Wed, Mar 22, 2017 at 5:30 PM, Bram Moolenaar wrote: > Ken Takata wrote: > > > 2016/2/18 Thu 4:48:46 UTC+9 Bram Moolenaar wrote: > > > > Mac OS has also some default mappings, but it seems that they are not > > > > documented. > > > >

Re: Compiler warnings in 8.0.453

On Sunday, March 12, 2017 at 3:41:17 PM UTC-4, Manuel Ortega wrote: > On macOS 10.12.3 Sierra, there have suddenly (within the last day, I think) > appeared compiler warnings during the make phase.  This is Vim 8.0.453.  See > below. > > > -Manny [SNIP] Bisection reveals t

Compiler warnings in 8.0.453

On macOS 10.12.3 Sierra, there have suddenly (within the last day, I think) appeared compiler warnings during the make phase. This is Vim 8.0.453. See below. -Manny gcc -c -I. -Iproto -DHAVE_CONFIG_H -DMACOS_X_UNIX -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o objects/screen.o

Re: More test litter

On Tue, Mar 7, 2017 at 9:54 AM, Manuel Ortega <mannyvim...@gmail.com> wrote: > > The file I originally reported still reappears after doing a `git clean > -fdx` and starting over. > > I applied Christian's patch. This stopped src/testdir/xxx from > reappearing as an untr

Re: More test litter

On Tue, Mar 7, 2017 at 3:25 AM, Christian Brabandt <cbli...@256bit.org> wrote: > On So, 05 Mär 2017, Bram Moolenaar wrote: > > Manuel Ortega wrote: > > > > > After a build and a `make clean`, I now find that `git status` shows: > > > "src/testdir/xxx&qu

More test litter

After a build and a `make clean`, I now find that `git status` shows: "src/testdir/xxx" as an untracked item. This should either get cleaned up by `make clean`, or be gitignored. -Manny -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the

Re: Patch 8.0.0364

On Sat, Feb 25, 2017 at 8:21 AM, Bram Moolenaar <b...@moolenaar.net> wrote: > > Patch 8.0.0364 > Problem:]s does not move cursor with two spell errors in one line. > (Manuel > Ortega) > Solution: Don't stop search immediately when wrapped,

Re: The ]s command broke recently

On Thu, Feb 23, 2017 at 10:10 PM, Ken Takata <ktakata65...@gmail.com> wrote: > Hi, > > 2017/2/24 Fri 8:42:16 UTC+9 Manuel Ortega wrote: > > The ]s command for moving to the next spelling error has become broken > recently. Sometime within the last three weeks I would g

The ]s command broke recently

The ]s command for moving to the next spelling error has become broken recently. Sometime within the last three weeks I would guess. Create a text file called "foo" containing the following text (one line): This was a tricky problem. We're given a sheep, and a shoezp where A is the incumbent

Re: test failures on macOS 10.12.2

On Tuesday, January 10, 2017 at 1:31:03 PM UTC-6, Manuel Ortega wrote: > On macOS 10.12.2, with a fresh pull of the repo up to 8.0.169, there are > suddenly test failures: > > > > VIMRUNTIME=../../runtime; export VIMRUNTI

test failures on macOS 10.12.2

On macOS 10.12.2, with a fresh pull of the repo up to 8.0.169, there are suddenly test failures: VIMRUNTIME=../../runtime; export VIMRUNTIME; ../vim -f -u unix.vim -U NONE --noplugin --not-a-term -U NONE -S runtest.vim test_channel.vim Vim:

Re: Vim 25 birthday presentation

On Wed, Dec 14, 2016 at 2:39 PM, Bram Moolenaar wrote: > > Hello Vim users! > > On November 2nd I did a presentation about Vim at Google Zurich. > This is exactly 25 years since the first public version of Vim was > built. > Dear Bram, Since the audio is bad, would you mind

Re: [vim/vim] make line commands use visual lines in softwrap (enhancement) (#1164)

On Thu, Oct 13, 2016 at 4:00 PM, yashamon wrote: > What about D, V command, etc? these behave terribly with wrapped text. > For the D command, just do dg$. If you don't like typing three characters, make up a mapping. -Manny -- -- You received this message from

Re: omission in :h file-pattern?

On Thu, Sep 1, 2016 at 1:46 AM, Christian Brabandt <cbli...@256bit.org> wrote: > Am 2016-09-01 07:41, schrieb Dominique Pellé: > >> Manuel Ortega <mannyvim...@gmail.com> wrote: >> >> The docs at :h file-pattern don't mention it, but I seem to be able to use &g

omission in :h file-pattern?

The docs at :h file-pattern don't mention it, but I seem to be able to use "\=" just fine in autocmd patterns, and it seems to mean what it means in :h pattern-overview ("zero or one"). For instance, `au SomeGroup *.[xgb]z2\= some_command` will fire on files with any of the following extensions:

Small doc fixes for lambda

At ":h lambda", there is some erroneous markup. It mistakenly is "|expr1|", which takes the user to the help for the ternary conditional! I think what was meant was "{expr1}", but even better would just be "{expr}". The following diff fixes it, along with one tiny, unrelated omission. -Manny

Re: Diff should indicate if no differences detected

On Sun, Aug 28, 2016 at 6:05 AM, toothpik wrote: > 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

Re: Diff should indicate if no differences detected

On Sat, Aug 27, 2016 at 11:32 PM, 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.

Re: Changing the defaults with Vim 8

On Wed, Jul 27, 2016 at 1:31 PM, Kazunobu Kuriyama < kazunobu.kuriy...@gmail.com> wrote: > > It may be true that setting go+=M will reduce memory usage and make > startup faster. But I would say the benefit gained by doing that is quite > marginal. > It makes a noticeable difference to me.

Re: Changing the defaults with Vim 8

Perhaps another way to fix this would be if the user could have a ~/.vim/menu.vim that is treated like ~/.vim/filetype.vim is treated. I.e., that Vim will load the ~/.vim/menu.vim before it loads $VIMRUNTIME/menu.vim. That way, a user could in his own ~/.vim/menu.vim set some variables that will

Re: Changing the defaults with Vim 8

On Wed, Jul 27, 2016 at 1:47 PM, Gary Johnson <garyj...@spocom.com> wrote: > On 2016-07-27, Manuel Ortega wrote: > > On Wed, Jul 27, 2016 at 12:26 PM, Gary Johnson wrote: > > > > On 2016-07-27, Manuel Ortega wrote: > > > > > What if "syntax

Re: Changing the defaults with Vim 8

On Wed, Jul 27, 2016 at 11:40 AM, Manuel Ortega <mannyvim...@gmail.com> wrote: > >> I agree that "syntax on" and "filetype on" (maybe even "filetype plugin >> indent on") are pretty core features that should probably be enabled by >> defaul

Re: Changing the defaults with Vim 8

On Wed, Jul 27, 2016 at 3:51 AM, Manuel Ortega <mannyvim...@gmail.com> wrote: > On Wed, Jul 27, 2016 at 2:51 AM, Manuel Ortega <mannyvim...@gmail.com> > wrote: > >> On Tue, Jul 26, 2016 at 5:17 PM, Bram Moolenaar <b...@moolenaar.net> >> wrote: >> >

Re: Changing the defaults with Vim 8

On Wed, Jul 27, 2016 at 2:51 AM, Manuel Ortega <mannyvim...@gmail.com> wrote: > On Tue, Jul 26, 2016 at 5:17 PM, Bram Moolenaar <b...@moolenaar.net> > wrote: > >> >> >> " Switch syntax highlighting on when the terminal has colors or when >> using

Re: Changing the defaults with Vim 8

On Tue, Jul 26, 2016 at 5:17 PM, Bram Moolenaar wrote: > > " Only do this part when compiled with support for autocommands. > if has("autocmd") > > " Enable file type detection. > " Use the default filetype settings, so that mail gets 'tw' set to 72, > " 'cindent' is on

Re: Changing the defaults with Vim 8

On Mon, Jul 25, 2016 at 4:00 PM, Bram Moolenaar wrote: > > Hirohito Higashi wrote: > > > I think it is better to change the default value of Vim body for some > > of the options. > > > > i.e. > > set wildmenu > > set ruler > > set showcmd > > set tags=./tags;,tags; > > etc...

Re: Patch 7.4.2102

On Mon, Jul 25, 2016 at 2:00 PM, Manuel Ortega <mannyvim...@gmail.com> wrote: > > > On Mon, Jul 25, 2016 at 1:41 PM, Hisashi T Fujinaka <ht...@twofifty.com> > wrote: > >> >> Well, --huge is breaking on OSX for me again. I'm seeing if I can figure >>

Re: Patch 7.4.2102

On Mon, Jul 25, 2016 at 1:41 PM, Hisashi T Fujinaka wrote: > > Well, --huge is breaking on OSX for me again. I'm seeing if I can figure > out where it broke. I wish I knew how to use bisect... > What are your ./configure flags? I am building with huge features on OSX with

Re: Changing the defaults with Vim 8

On Sun, Jul 24, 2016 at 12:09 PM, Manuel Ortega <mannyvim...@gmail.com> wrote: > On Sun, Jul 24, 2016 at 9:02 AM, Bram Moolenaar <b...@moolenaar.net> > wrote: > >> >> >> Probably not: >> >> " these two leave files behind >> s

Re: Changing the defaults with Vim 8

On Sun, Jul 24, 2016 at 9:02 AM, Bram Moolenaar wrote: > > Vim has always been conservative about the default option values. > Without any .vimrc the default is 'compatible'. That's nice for people > who rely on the old Vi. But how many of these still exist? I expect >

Re: Syntax highlight error in .vim ??

On Thu, Jul 21, 2016 at 3:46 PM, Charles E Campbell < drc...@campbellfamily.biz> wrote: > Ken Takata wrote: > > Hi, > > > > 2016/7/20 Wed 13:41:57 UTC+9 Tony Mechelynck wrote: > >> On Wed, Jul 20, 2016 at 4:55 AM, skywind3...@163.com > >> wrote: > >>> Reproduce: > >>> 1. vim

Re: Why isn't shelltemp=0 the default?

On Sun, Jul 10, 2016 at 1:23 PM, Bram Moolenaar <b...@moolenaar.net> wrote: > > Manuel Ortega wrote: > > > On Saturday, June 14, 2014 at 11:51:59 AM UTC-4, Justin M. Keyes wrote: > > > With shelltemp=0, Vim automatically falls back to using temp files if > &

Re: screen garbled when using execute()

On Sunday, July 10, 2016 at 8:49:41 AM UTC-4, Bram Moolenaar wrote: > Manuel Ortega wrote: > > > I'm seeing some screen rendering problems with the new execute() > > function. > > > > To reproduce: > > > > vim -u NONE -N somenonemptyfile > >

Re: Why isn't shelltemp=0 the default?

On Saturday, June 14, 2014 at 11:51:59 AM UTC-4, Justin M. Keyes wrote: > With shelltemp=0, Vim automatically falls back to using temp files if > pipes don't work. So why isn't shelltemp=0 the default? > > If I understand correctly, 'shelltemp' affects: > > :! > :w !foo > :r !foo > > But it

screen garbled when using execute()

I'm seeing some screen rendering problems with the new execute() function. To reproduce: vim -u NONE -N somenonemptyfile :echo execute("!ls") I expect: the same thing that "redir=>h | !ls |redir END | echo h" shows, i.e., ":!ls", except without a HIT ENTER prompt. I see: ":!ls" and a HIT ENTER

Re: A plea against the name "execute()"

> > call and call() are also. But I don't think it makes confusing. But it does, for new users and people learning VimScript. I'm not confused *anymore* about :substitute/substitute(), because I've now done a ton of vimscripting. But when I was new, I can't tell you how many times that messed

A plea against the name "execute()"

I don't have positive suggestion for an alternative, but... Please, please don't name the new function "execute()". It only breeds confusion because there is already a command called "execute". It really sucks when this happens, like with substitute() and :substitute. New users get confused,

7.4.1999 brings test failures on Mac OS X

`make test` results in the following on OS X 10.11.5, and patch 7.4.1999. Didn't happen with 7.4.1997. Executed 101 tests 1 FAILED: Found errors in Test_evalcmd(): function RunTheTest[9]..Test_evalcmd line 17: command did not fail: call evalcmd("call NestedRedir()") >From test_alot.vim: Found

Intermittent test failures on OS X 10.11.5

Sometimes, but not always (I would say 1 out of 5 times) building and testing after a `git clean -fdx` results in the following: >From test_channel.vim: Found errors in Test_call(): function RunTheTest[9]..Test_call[2]..3_run_server line 37: 'Can''t start test_channel.py' TEST FAILURE make[2]:

Re: is causing display artifacts in the GUI

On Wed, Jun 15, 2016 at 10:23 AM, Kazunobu Kuriyama < kazunobu.kuriy...@gmail.com> wrote: > 2016-06-15 23:02 GMT+09:00 Manuel Ortega <mannyvim...@gmail.com>: > >> On Wed, Jun 15, 2016 at 5:48 AM, Kazunobu Kuriyama < >> kazunobu.kuriy...@gmail.com> wrote:

Re: is causing display artifacts in the GUI

On Wed, Jun 15, 2016 at 10:02 AM, Manuel Ortega <mannyvim...@gmail.com> wrote: > On Wed, Jun 15, 2016 at 5:48 AM, Kazunobu Kuriyama < > kazunobu.kuriy...@gmail.com> wrote: > >> I couldn't reproduce the bug with Athena, GTK+ 2, GTK+ 3 GUIs, but did >> with MacVim

  1   2   3   >