Re: Odd behavior of vim 8.0.1203 in a wide xterm -- solution found

2017-11-03 Fir de Conversatie Gary Johnson
On 2017-11-03, Bram Moolenaar wrote: > Christian Brabandt wrote: > > > On Do, 02 Nov 2017, Gary Johnson wrote: > > > > > On 2017-11-02, Gary Johnson wrote: > > > > > > > So the funny behavior does seem related to the old addressing > > > > style, but why is it happening on an xterm-318 with

Re: Odd behavior of vim 8.0.1203 in a wide xterm -- solution found

2017-11-03 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: > On Do, 02 Nov 2017, Gary Johnson wrote: > > > On 2017-11-02, Gary Johnson wrote: > > > > > So the funny behavior does seem related to the old addressing > > > style, but why is it happening on an xterm-318 with 'ttymouse' > > > automatically set to "sgr"? > > > > I

Re: Security risk of vim swap files

2017-11-03 Fir de Conversatie Marvin Renich
* Zdenek Dohnal [171103 09:27]: > On 11/03/2017 02:07 PM, Marvin Renich wrote: > > * zdoh...@redhat.com [171103 03:45]: > Can other users open original file, which has .swp file belonging to > certain user:group with permissions 0600, as read-only with

Re: Security risk of vim swap files

2017-11-03 Fir de Conversatie Bram Moolenaar
Someone wrote: > Another option would be to copy the user and other permissions from the > original file, but reset the group permissions to 0. For example, if a > user goes to edit a file with permissions 754, the .swp file would have > the permissions 704. This prevents the security problem

Re: Odd behavior of vim 8.0.1203 in a wide xterm -- solution found

2017-11-03 Fir de Conversatie Gary Johnson
On 2017-11-03, Christian Brabandt wrote: > > On Do, 02 Nov 2017, Gary Johnson wrote: > > > On 2017-11-02, Gary Johnson wrote: > > > > > So the funny behavior does seem related to the old addressing > > > style, but why is it happening on an xterm-318 with 'ttymouse' > > > automatically set to

Re: Security risk of vim swap files

2017-11-03 Fir de Conversatie Zdenek Dohnal
On 11/03/2017 02:07 PM, Marvin Renich wrote: > * zdoh...@redhat.com [171103 03:45]: >>> Another solution would be to always use the editing user's user:group >>> and perm 0600. >> I agree with this solution. And IMO the best way would be to create >> option for configure

Re: Security risk of vim swap files

2017-11-03 Fir de Conversatie Z5T1
Another option would be to copy the user and other permissions from the original file, but reset the group permissions to 0. For example, if a user goes to edit a file with permissions 754, the .swp file would have the permissions 704. This prevents the security problem with .swp files while still

Re: Security risk of vim swap files

2017-11-03 Fir de Conversatie Marvin Renich
* zdoh...@redhat.com [171103 03:45]: > > Another solution would be to always use the editing user's user:group > > and perm 0600. > > I agree with this solution. And IMO the best way would be to create > option for configure script+create option for vimrc configuration >

Re: Odd behavior of vim 8.0.1203 in a wide xterm -- solution found

2017-11-03 Fir de Conversatie Christian Brabandt
On Do, 02 Nov 2017, Gary Johnson wrote: > On 2017-11-02, Gary Johnson wrote: > > > So the funny behavior does seem related to the old addressing > > style, but why is it happening on an xterm-318 with 'ttymouse' > > automatically set to "sgr"? > > I tried finding the problem by bisecting the

Re: Security risk of vim swap files

2017-11-03 Fir de Conversatie zdohnal
On Friday, November 3, 2017 at 8:44:51 AM UTC+1, zdo...@redhat.com wrote: > > Another solution would be to always use the editing user's user:group > > and perm 0600. > > I agree with this solution. And IMO the best way would be to create option > for configure script+create option for vimrc

Re: Security risk of vim swap files

2017-11-03 Fir de Conversatie zdohnal
> Another solution would be to always use the editing user's user:group > and perm 0600. I agree with this solution. And IMO the best way would be to create option for configure script+create option for vimrc configuration file, which can turn on/off this behavior (IMHO it's good to have option

Re: issue with build-in omni func

2017-11-03 Fir de Conversatie Christian Brabandt
On Fr, 03 Nov 2017, 世东 王 wrote: > Hi. here is an issue about omnifunc > > https://github.com/neovim/neovim/issues/7471 > > I am not sure why I can not login my github account, so here is the old link > I just post. That has just been fixed as mentioned in the github issue. Christian --

Re: How about add a new key to setqflist()

2017-11-03 Fir de Conversatie Shidong Wang
在 2017年10月18日星期三 UTC+8上午12:07:36，Shidong Wang写道： > when using quickfix list, if the filename is too long, it is hard to read the > `text` of each item of the list. I think we should add a new key, such as > `abbr`, this will be deplayed if it is not a empty string instead of > `filename` or

issue with build-in omni func

2017-11-03 Fir de Conversatie 世东 王
Hi. here is an issue about omnifunc https://github.com/neovim/neovim/issues/7471 I am not sure why I can not login my github account, so here is the old link I just post. Shidong Wang -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the