Re: VIM and NTFS streams

2008-02-06 Fir de Conversatie Bram Moolenaar
Alex Jakushev wrote: On 1/31/08, Bram Moolenaar [EMAIL PROTECTED] wrote: Try setting the 'backupcopy' option to yes. This worked, but then it raises another question. Previous value of the 'backupcopy' option was auto, which means yes or no, which works best. Why didn't it choose

Re: VIM and NTFS streams

2008-02-06 Fir de Conversatie Alexei Alexandrov
krischik wrote: I fear you missed something - since NTFS v3.0 named forks are supported. They are called Alternate data streams. Oops, yep, I have a lot of stuff to catch up with. -- Alexei Alexandrov --~--~-~--~~~---~--~~ You received this message from

Re: VIM and NTFS streams

2008-02-05 Fir de Conversatie krischik
On 5 Feb., 00:12, Ben Schmidt [EMAIL PROTECTED] wrote: And that sad story told, I do agree with the other posters who don't think this has much use in Vim. I think to have some kind of consistency, probably an OS or other fairly central component needs to lead the way, not a text editor.

Re: VIM and NTFS streams

2008-02-05 Fir de Conversatie krischik
On 4 Feb., 23:09, Matt Wozniski [EMAIL PROTECTED] wrote: On Feb 4, 2008 4:29 PM, krischik wrote: On 4 Feb., 21:10, Matt Wozniski wrote: While this would be nice, it would require support code from every application you have. It may only be 6 lines, but 6 lines * 5000 binaries is

Re: VIM and NTFS streams

2008-02-05 Fir de Conversatie Tony Mechelynck
krischik wrote: [...] I would use cp --archive test.txt test2.txt in which case the EA's are copied as well. At least on SuSE Linux 9.2 onwards. And of course the file would still be UTF-16 - after all it's copy not convert. Without meaning offence: You should read up a little on the

Re: VIM and NTFS streams

2008-02-05 Fir de Conversatie krischik
On 5 Feb., 11:37, Tony Mechelynck [EMAIL PROTECTED] wrote: krischik wrote: [...] I would use cp --archive test.txt test2.txt in which case the EA's are copied as well. At least on SuSE Linux 9.2 onwards. And of course the file would still be UTF-16 - after all it's copy not convert.

Re: VIM and NTFS streams

2008-02-05 Fir de Conversatie Paul LeoNerd Evans
On Tue, 5 Feb 2008 02:25:26 -0800 (PST) krischik [EMAIL PROTECTED] wrote: Sad that everybody else only sees only hurdles and risks of change and not the chances and the risk of no-change. And yes: there is a rist of no-change! I have to agree with krischik here. At University, I once got

Re: VIM and NTFS streams

2008-02-05 Fir de Conversatie krischik
On 5 Feb., 12:55, Paul LeoNerd Evans [EMAIL PROTECTED] wrote: I also know that the lighttpd webserver uses them by default, only falling back on filename-based detection if the file doesn't have a Content-Type EA. Funny as you say - on my research for my little rants here (yes I do research

Re: VIM and NTFS streams

2008-02-05 Fir de Conversatie Alexei Alexandrov
krischik wrote: Open a console and type man 5 attr? Or look here: http://linux.die.net/man/5/attr No it has nothing to do with Linux. FreeBSD, Solaris and Mac OS X support extended attributes as well. See: http://en.wikipedia.org/wiki/Extended_file_attributes Quote Wikipedia:

Re: VIM and NTFS streams

2008-02-04 Fir de Conversatie krischik
On 4 Feb., 15:18, krischik [EMAIL PROTECTED] wrote: And it is precisely those simple abstractions (files/directories) available on all modern systems  which bring those problems. Only: It's not modern systems - it's between 1 and 2 decades old systems. Truly modern operating systems support

Re: VIM and NTFS streams

2008-02-04 Fir de Conversatie krischik
On 4 Feb., 21:10, Matt Wozniski [EMAIL PROTECTED] wrote: On Feb 4, 2008 9:18 AM, krischik wrote: On the other hand use of extended attributes could solve a problem with 5 lines of code where solving the same problem without could cost you 50. Determine file types, text file line

Re: VIM and NTFS streams

2008-02-04 Fir de Conversatie Matt Wozniski
On Feb 4, 2008 9:18 AM, krischik wrote: On the other hand use of extended attributes could solve a problem with 5 lines of code where solving the same problem without could cost you 50. Determine file types, text file line endings and text file encoding come to my mind here. Ask Bram how

Re: VIM and NTFS streams

2008-02-04 Fir de Conversatie Matt Wozniski
On Feb 4, 2008 4:29 PM, krischik wrote: On 4 Feb., 21:10, Matt Wozniski wrote: While this would be nice, it would require support code from every application you have. It may only be 6 lines, but 6 lines * 5000 binaries is much more code than is in vim for line ending detection. But

Re: VIM and NTFS streams

2008-02-04 Fir de Conversatie Ben Schmidt
Ben Schmidt wrote: Ahh, indeed, there is the problem and the reason why computing has not advanced as much in the last 15 years as one would have expected seeing the 15 years before: Backward compatibilty has hobbled us. Indeed, I think it has. The Mac OS used to use resource forks and type

RE: VIM and NTFS streams

2008-01-31 Fir de Conversatie Craig Barkhouse
Alexei Alexandrov wrote: 2 notes here: 1. I think NTFS streams is useless feature. I've never seen any practical example of the usefulness of this. For my own purposes, I agree. However, some users and some applications will find uses for streams (same can be said of any feature). It

Re: VIM and NTFS streams

2008-01-31 Fir de Conversatie Andy Wokula
Alexei Alexandrov schrieb: Alex wrote: Hi all, I understand that these bugs and feature requests are nice to have, but anyway... VIM is not working very well with NTFS streams. When you edit file, say, test.txt:aaa, it complains about backup during save (E510). If you edit file