On 2016-01-15 10:06, Bram Moolenaar wrote:
> I think most users will be in this situation:
>
> - Initially check out Vim from github:
>
> git clone https://github.com/vim/vim.git
>
> - Change a makefile to set some options, or change bigvim.bat to match
> your Python version, etc.
>
> -
On 2016-01-18 03:36, LCD 47 wrote:
> It does, "git br -u" is a shortcut for "git branch --set-upstream-to".
Uh... really? It is on *my* machine because I have a whole bunch of
svn-style aliases set up. Where did *you* get these from? They don't
appear to be part of "stock git", at least not wi
On 2015-08-14 14:38, Bram Moolenaar wrote:
> Hmm, one can add a repository and delete a repository, but making it
> totally empty and pushing a fresh repo into it appears not to be
> possible.
As far as non-git content (e.g. issues, pull requests), that may be true.
To empty out the git bits of a
On 2014-02-03 13:24, Gary Johnson wrote:
On 2014-02-03, nag wrote:
I am working on RHEL 5.9 systems. The default installed vim editor
is not working fully. My problems:
No syntax highlighting.
No cursor position display
No column and row numbers.
No visual selection (visual block, ctrl+v)
curso
On 2013-09-17 15:59, Ben Fritz wrote:
On Tuesday, September 17, 2013 12:17:57 PM UTC-5, Matthew Woehlke wrote:
I just discovered that text wrapping has changed at least between
vim-enhanced-7.3.1314-2.fc18.x86_64 and
vim-enhanced-7.4.016-1.fc18.x86_64 (so probably between 7.3.x and 7.4.0).
It
I just discovered that text wrapping has changed at least between
vim-enhanced-7.3.1314-2.fc18.x86_64 and
vim-enhanced-7.4.016-1.fc18.x86_64 (so probably between 7.3.x and 7.4.0).
It used to be the case that if I typed some text that was almost long
enough to wrap, then went to the beginning o
dickey wrote:
> Bram Moolenaar wrote:
>> Do all the terminals supporting 88 and 256 colors really use the same
>> color values?
>
> [snip]
> Like konsole, it uses (even) more memory but comes with prettier
> menus.
Konsole seems to support 16777216 colors.
$ echo -e '\e[38;2;128;160;128mhello\e[
SungHyun Nam wrote:
> If I edit a file with a win32 vim, then the file mode in
> CYGWIN is changed to 0755.
>
> Is it possible win32 vim preserves the file mode in cygwin?
Windows programs don't know about Cygwin file permissions.
If vim is changing the Windows ACL permissions (hint: cacls, or
Try #4...
Bram Moolenaar wrote:
> Per Hallsmark wrote:
>> Is it possible to have this reworked so that vim follows same
>> scheme as about 99% of the rest of the world does? :)
>
> A change like this will break existing build scripts.
Alternatively, a change like this will allow existing build
