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

On Thursday, June 9, 2016 at 7:05:58 PM UTC-4, Ben Fritz wrote: > On Thu, Jun 9, 2016 at 2:56 PM, Charles E Campbell > wrote: > >  if libraries are used, the system may update the library (while one > > is on holiday), potentially rendering encrypted text unreadable. 

Re: File format issues when using gpg

On Thursday, June 9, 2016 at 8:20:51 PM UTC-4, James McCoy wrote: > On Thu, Jun 09, 2016 at 10:19:09AM -0700, cryptoz wrote: > > I did not more digging and realized that vim has already had a mechanisms to > > transform input/output streams. I will try BufReadCmd/BufWriteCmd later. > > > You

Re: RFC: New functions to get information about buffers, windows and tab pages

Hi Christian, On Wed, Jun 8, 2016 at 11:16 PM, Christian Brabandt wrote: > Hi Yegappan, > > good to see some work on this. Just some quick notes. > Thanks for reviewing this. > > Am 2016-06-09 05:29, schrieb Yegappan Lakshmanan: >> >> Hi all, >> >> I have created the

Re: File format issues when using gpg

On Thursday, June 9, 2016 at 1:53:05 AM UTC-5, cryptoz wrote: > > The script I put in _vimrc to open *.gpg,*.asc files is similar to what I > got from http://vim.wikia.com/wiki/Encryption > > I understand correctly, the steps are: > > 1. set bin option before read the file. > 2. read the file

Re: core dumps during signal handling

On Thu, Jun 09, 2016 at 10:53:16PM +0200, Bram Moolenaar wrote: > > Danek Duvall wrote: > > The thought I have was to do the classic thing where the signal handler > > sets a global flag and returns immediately. For the majority of the cases > > I've seen, the loop in RealWaitForChar is where

Re: File format issues when using gpg

On Thu, Jun 09, 2016 at 10:19:09AM -0700, cryptoz wrote: > I did not more digging and realized that vim has already had a mechanisms to > transform input/output streams. I will try BufReadCmd/BufWriteCmd later. You might be interested in my vim-gnupg plugin --

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

On Thu, Jun 9, 2016 at 2:56 PM, Charles E Campbell < drc...@campbellfamily.biz> wrote: > if libraries are used, the system may update the library (while one > is on holiday), potentially rendering encrypted text unreadable. I know > that these things should be done in a backwards compatible

Re: [vim/vim] ftplugin/python.vim: improve matching for ]] [[ ]m [m (#842)

James Sully wrote: > Attached :) > > And, created https://github.com/sullyj3/vim-ftplugin-python Thanks. Let's add the previous maintainer to the header: " Previous Maintainer: Johannes Zellner -- If your nose runs, and your feet smell, you might be upside down.

Patch 7.4.1913

Patch 7.4.1913 Problem:When ":doautocmd" is used modelines are used even when no autocommands were executed. (Daniel Hahler) Solution: Skip processing modelines. (closes #854) Files: src/fileio.c, src/ex_cmds.c, src/ex_docmd.c, src/proto/fileio.pro ***

Re: core dumps during signal handling

Danek Duvall wrote: > I've been chasing down a bug in vim, where killing vim (usually via SIGHUP > or SIGTERM) causes it to get a SIGSEGV and dump core. I'm doing my work on > Solaris, but I can get it to do the same thing on Ubuntu 14.04, so it's not > strictly a Solaris thing. Hmm, killing

Re: Patch 7.4.1890

On Saturday, June 4, 2016 at 5:24:42 PM UTC+3, Bram Moolenaar wrote: > Patch 7.4.1890 > Problem:GUI: When channel data is received the cursor blinking is > interrupted. (Ramel Eshed) > Solution: Don't update the cursor when it is blinking. > Files: src/screen.c,

Patch 7.4.1912

Patch 7.4.1912 Problem:No test for using setqflist() on an older quickfix list. Solution: Add a couple of tests. Files: src/testdir/test_quickfix.vim *** ../vim-7.4.1911/src/testdir/test_quickfix.vim 2016-05-25 21:22:56.421828207 +0200 --- src/testdir/test_quickfix.vim

Re: Asynchronous grep plugin - thoughts and issues

I wrote: > Ramel Eshed wrote: > > > > > 1) Actually, there is a bug here which is not exactly what I've > > > > described earlier. The issue is that :call setqflist([]), instead of > > > > adding one more list after the last list, will clear the next list and > > > > delete the ones after. For

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: Asynchronous grep plugin - thoughts and issues

On Thursday, June 9, 2016 at 6:53:06 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > > > 1) Actually, there is a bug here which is not exactly what I've > > > > described earlier. The issue is that :call setqflist([]), instead of > > > > adding one more list after the last list, will

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

Benjamin Fritz wrote: > > On Wed, Mar 23, 2016 at 4:58 PM, Bram Moolenaar > wrote: > > > > > Speaking of defaults: I think Vim should default to the strongest > > > method available. I additionally think Vim should warn on saving with > > > a known

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] ftplugin/python.vim: improve matching for ]] [[ ]m [m (#842)

Attached :) And, created https://github.com/sullyj3/vim-ftplugin-python On Fri, 10 Jun 2016 at 00:45 Christian Brabandt wrote: > Am 2016-06-09 09:14, schrieb James Sully: > > I'd absolutely be willing, the main issue is whether I'm able. I don't > > actually know vimscript

Patch 7.4.1911

Patch 7.4.1911 Problem:Recent history lines may be lost when exiting Vim. Solution: Merge history using the timestamp. Files: src/ex_getln.c, src/ex_cmds.c, src/vim.h, src/proto/ex_getln.pro, src/testdir/test_viminfo.vim *** ../vim-7.4.1910/src/ex_getln.c 2016-06-06

core dumps during signal handling

I've been chasing down a bug in vim, where killing vim (usually via SIGHUP or SIGTERM) causes it to get a SIGSEGV and dump core. I'm doing my work on Solaris, but I can get it to do the same thing on Ubuntu 14.04, so it's not strictly a Solaris thing. Most reproducibly (for me, at least), it

Re: File format issues when using gpg

I did not more digging and realized that vim has already had a mechanisms to transform input/output streams. I will try BufReadCmd/BufWriteCmd later. Thanks. On Thursday, June 9, 2016 at 9:34:42 AM UTC-4, cryptoz wrote: > On Thursday, June 9, 2016 at 5:34:10 AM UTC-4, Ken Takata wrote: > > Hi

Re: Asynchronous grep plugin - thoughts and issues

Ramel Eshed wrote: > > > 1) Actually, there is a bug here which is not exactly what I've > > > described earlier. The issue is that :call setqflist([]), instead of > > > adding one more list after the last list, will clear the next list and > > > delete the ones after. For example: let's say I

Re: [vim/vim] ftplugin/python.vim: improve matching for ]] [[ ]m [m (#842)

Am 2016-06-09 09:14, schrieb James Sully: I'd absolutely be willing, the main issue is whether I'm able. I don't actually know vimscript (this patch is super trivial). I'd love to learn and give it a shot though. Is there a document somewhere that outlines the responsibilities and process?

Re: vim.exe doesn't restore wide characters in cmd.exe

On Wednesday, June 8, 2016 at 1:13:48 AM UTC+9, Ken Takata wrote: > Hi mattn and all, > > 2015/5/25 Mon 13:15:09 UTC+9 mattn wrote: > > http://go-gyazo.appspot.com/07b65df3b2cdd94b.png > > > > Since vim.exe uses ReadConsoleOutputA/WriteConsoleOutputA, wide characters > > are not remained on

Re: File format issues when using gpg

On Thursday, June 9, 2016 at 5:34:10 AM UTC-4, Ken Takata wrote: > Hi cryptoz, > > 2016/6/9 Thu 15:53:05 UTC+9 cryptoz wrote: > > I have followed instructions on the Internet to edit gpg encrypted text > > file transparently. It almost works, but the file format is messed up for > > gpg files.

Re: Asynchronous grep plugin - thoughts and issues

On Thursday, June 9, 2016 at 11:52:41 AM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > 1) Actually, there is a bug here which is not exactly what I've > > described earlier. The issue is that :call setqflist([]), instead of > > adding one more list after the last list, will clear the

Re: File format issues when using gpg

Hi cryptoz, 2016/6/9 Thu 15:53:05 UTC+9 cryptoz wrote: > I have followed instructions on the Internet to edit gpg encrypted text file > transparently. It almost works, but the file format is messed up for gpg > files. > > OS: Windows 10. > vim version: 7.4.1023 and 7.4.1721 (tried both) > >

Re: Any way to scroll quickfix window automatically for long-time-running jobs ?

Marius Gedminas wrote: > On Wed, Jun 08, 2016 at 10:33:55PM +0200, Christian Brabandt wrote: > > Hi skywind3000! > > > > On Do, 09 Jun 2016, skywind3...@163.com wrote: > > > > > ":cbottom" seems more adaptive than auto scroll > > > > Why? I think it has been shown, that depending on the use

Re: Asynchronous grep plugin - thoughts and issues

Ramel Eshed wrote: > 1) Actually, there is a bug here which is not exactly what I've > described earlier. The issue is that :call setqflist([]), instead of > adding one more list after the last list, will clear the next list and > delete the ones after. For example: let's say I used :grep 4

Re: File format issues when using gpg

Ah, please ignore my pointless reply. sorry. -- -- 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 message because you are subscribed

Re: File format issues when using gpg

Hi cryptoz, 2016-6-9(Thu) 15:53:05 UTC+9 cryptoz: > I have followed instructions on the Internet to edit gpg encrypted text file > transparently. It almost works, but the file format is messed up for gpg > files. > > OS: Windows 10. > vim version: 7.4.1023 and 7.4.1721 (tried both) > >

Re: Any way to scroll quickfix window automatically for long-time-running jobs ?

On Wed, Jun 08, 2016 at 10:33:55PM +0200, Christian Brabandt wrote: > Hi skywind3000! > > On Do, 09 Jun 2016, skywind3...@163.com wrote: > > > ":cbottom" seems more adaptive than auto scroll > > Why? I think it has been shown, that depending on the use case auto > scroll does not make sense

File format issues when using gpg

I have followed instructions on the Internet to edit gpg encrypted text file transparently. It almost works, but the file format is messed up for gpg files. OS: Windows 10. vim version: 7.4.1023 and 7.4.1721 (tried both) Problems: Suppose I have a file a.txt. It has only one character in it

Re: RFC: New functions to get information about buffers, windows and tab pages

Hi Yegappan, good to see some work on this. Just some quick notes. Am 2016-06-09 05:29, schrieb Yegappan Lakshmanan: Hi all, I have created the following new functions to return information about buffers, windows and tabpages. Pull request: https://github.com/vim/vim/pull/833 1. Function: