Re: write-region is mishandling an error
On 2/9/07, Richard Bielawski <[EMAIL PROTECTED]> wrote: No error. Data is 'technically' saved. No, data is not "technically" saved. It is just saved. To NTFS, writing on the default stream is no different that writing on a named stream. If this worked then I'd have to agree that there is nothing wrong. But since it doesn't I think you should either reject the original save attempt or let me read the data back. I've said that there's nothing wrong with NTFS streams, so we shouldn't think of ab:cd as an erroneous file name. You're saying there are things wrong with Emacs half-hearted treatment of streams. I agree. In fact, I think Emacs works with streams mostly by accident. You cannot do "C-x C-f ab:cd", for example. /L/e/k/t/u ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: write-region is mishandling an error
> > Yes, please. We have been discussing this before. > > Yes, and I think we decided that doing nothing was the best course of > action. I still agree. There's nothing wrong with streams. I think I need to disagree. It's true, Emacs developers can't be expected to document OS idiosyncrasies. But create a buffer and put any simple text in it. C-x C-w little:test No error. Data is 'technically' saved. It's not Emacs fault that it doesn't 'look' saved. BUT! M-x revert-buffer revert-buffer: Cannot revert nonexistent file f:/little:test If this worked then I'd have to agree that there is nothing wrong. But since it doesn't I think you should either reject the original save attempt or let me read the data back. Personally, because the things I could do with this are so cool, I hope you'll let me get the data back! For example I would no longer need to clutter documents with and explain -- LocalWords: * This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of CH Robinson. CH Robinson accepts no liability for any damage caused by any virus transmitted by this email. CH Robinson Worldwide, 8100 Mitchell Road, Eden Prairie, MN, USA * ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: write-region is mishandling an error
On 2/9/07, Stefan Monnier <[EMAIL PROTECTED]> wrote: Still I think it deserves a treatment similar to narrow-region (with which there's nothing wrong either): warn the user and force her to enable the "feature" before she can use it. OK. /L/e/k/t/u ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: write-region is mishandling an error
>> Yes, please. We have been discussing this before. > Yes, and I think we decided that doing nothing was the best course of > action. I still agree. There's nothing wrong with streams. I have no idea what they do, so I can't judge, but I believe you that there's nothing wrong with them. Still I think it deserves a treatment similar to narrow-region (with which there's nothing wrong either): warn the user and force her to enable the "feature" before she can use it. Stefan ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: write-region is mishandling an error
> From: Stefan Monnier <[EMAIL PROTECTED]> > Date: Fri, 09 Feb 2007 10:19:16 -0500 > Cc: emacs-pretest-bug@gnu.org, Richard Bielawski <[EMAIL PROTECTED]> > > Maybe Emacs should warn the user that she's about to use a little-known > corner of her OS semantics. Yes, I think we should add a warning and an option to shut up that warning. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: write-region is mishandling an error
On 2/9/07, Lennart Borgman (gmail) <[EMAIL PROTECTED]> wrote: Yes, please. We have been discussing this before. Yes, and I think we decided that doing nothing was the best course of action. I still agree. There's nothing wrong with streams. /L/e/k/t/u ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: write-region is mishandling an error
Stefan Monnier wrote: Which creates an empty file named "Test at 12" and no error occurs. Initially I didn't notice that the filename was truncated. Once I did I realized that : is illegal in a file name. Some kind of error must be occurring that isn't being reported. If you run under a debugger with a breakpoint at Fsignal you will see if any Emacs Lisp error occurs. I suspect you will find there is none; I suspect that Windows truncates the file name without complaining. "foo:bar" is a special thingy under WinNT (or maybe under NTFS), kind of like a "fork" in MacOS speech. It seems it's called "stream". Maybe Emacs should warn the user that she's about to use a little-known corner of her OS semantics. Yes, please. We have been discussing this before. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: write-region is mishandling an error
On 2/9/07, Stefan Monnier <[EMAIL PROTECTED]> wrote: "foo:bar" is a special thingy under WinNT (or maybe under NTFS), kind of like a "fork" in MacOS speech. It seems it's called "stream". NTFS. http://msdn2.microsoft.com/en-us/library/aa364404.aspx /L/e/k/t/u ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: write-region is mishandling an error
> Which creates an empty file named "Test at 12" and no error occurs. > Initially I didn't notice that the filename was truncated. > Once I did I realized that : is illegal in a file name. > Some kind of error must be occurring that isn't being reported. > If you run under a debugger with a breakpoint at Fsignal you will see > if any Emacs Lisp error occurs. I suspect you will find there is none; > I suspect that Windows truncates the file name without complaining. "foo:bar" is a special thingy under WinNT (or maybe under NTFS), kind of like a "fork" in MacOS speech. It seems it's called "stream". Maybe Emacs should warn the user that she's about to use a little-known corner of her OS semantics. Stefan ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: write-region is mishandling an error
Possibly, I don't have the tools you speak of to tell. But then where is the data going? If the filename was simply being truncated but the data was still being written then I suppose I'd believe no 'error' occurred; that the OS simply sees the : as a file name terminator and continues successfully. But the file is empty. So it seems I'm also being asked to believe that subsequent write operations are also not getting errors. Being a programmer myself I can't help but find a claim that data is being discarded by a modern OS without error hard to believe. -Original Message- From: Richard Stallman [mailto:[EMAIL PROTECTED] Sent: Friday, February 09, 2007 8:23 AM To: Richard Bielawski Cc: emacs-pretest-bug@gnu.org Subject: Re: write-region is mishandling an error Which creates an empty file named "Test at 12" and no error occurs. Initially I didn't notice that the filename was truncated. Once I did I realized that : is illegal in a file name. Some kind of error must be occurring that isn't being reported. If you run under a debugger with a breakpoint at Fsignal you will see if any Emacs Lisp error occurs. I suspect you will find there is none; I suspect that Windows truncates the file name without complaining. * This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of CH Robinson. CH Robinson accepts no liability for any damage caused by any virus transmitted by this email. CH Robinson Worldwide, 8100 Mitchell Road, Eden Prairie, MN, USA * ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: write-region is mishandling an error
Which creates an empty file named "Test at 12" and no error occurs. Initially I didn't notice that the filename was truncated. Once I did I realized that : is illegal in a file name. Some kind of error must be occurring that isn't being reported. If you run under a debugger with a breakpoint at Fsignal you will see if any Emacs Lisp error occurs. I suspect you will find there is none; I suspect that Windows truncates the file name without complaining. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
write-region is mishandling an error
I couldn't get my data into a file using with-temp-file. All I got was an empty file. I eventually traced this command (with-temp-file "Test at 12:05.txt" (insert "Hello")) down to * write-region(1 5 "Test at 12:05.txt" nil 0) Which creates an empty file named "Test at 12" and no error occurs. Initially I didn't notice that the filename was truncated. Once I did I realized that : is illegal in a file name. Some kind of error must be occurring that isn't being reported. Turning debug-on-error on didn't show an error either. In GNU Emacs 22.0.90.1 (i386-mingw-nt5.1.2600) of 2006-11-07 on W2ONE X server distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4) --cflags -Id:/g/include' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: ENU locale-coding-system: cp1252 default-enable-multibyte-characters: t Major mode: Lisp Interaction Minor modes in effect: flyspell-mode: t show-paren-mode: t recentf-mode: t global-hi-lock-mode: t hi-lock-mode: t cua-mode: t tabbar-mode: t eldoc-mode: t which-function-mode: t shell-dirtrack-mode: t encoded-kbd-mode: t tooltip-mode: t tool-bar-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t unify-8859-on-encoding-mode: t utf-translate-cjk-mode: t auto-compression-mode: t line-number-mode: t transient-mark-mode: t Recent input: C-j C-M-x w r i t e - r e g i o n C-h f Recent messages: Wrote f:/emacs/.emacs.bmk Saving bookmarks to file ~\.emacs.bmk...done Starting new Ispell process [default] ... For information about the GNU Project and its goals, type C-h C-p. Mark set Debug on Error enabled nil Mark set mouse-2, RET: find function's definition Loading emacsbug...done Rick Bielawski 952-683-4679 * This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of CH Robinson. CH Robinson accepts no liability for any damage caused by any virus transmitted by this email. CH Robinson Worldwide, 8100 Mitchell Road, Eden Prairie, MN, USA * ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
