Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

hanekomu (8123)

hanekomu
  (email not shown publicly)
http://hanekomu.at/blog/
AOL IM: hanekomu (Add Buddy, Send Message)

Go (Baduk) player and Perl hacker.

Journal of hanekomu (8123)

Friday September 12, 2008
02:43 AM

CPAN Gems: Proc::InvokeEditor

[ #37419 ]

New blog entry: "CPAN Gems: Proc::InvokeEditor" in my Perl blog.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I thought it would be useful for editing variables while in the debugger, but vim is leaving multiple newlines after exiting.

    • Yes, because Vim is a text editor and text files end with a newline. You have to tell it that the thing you’re working on is not a text file by invoking it with the -b switch.

      • vim-7.1 seems to be broken editing binary files.

        Even setting noeol, it is adding 4 or 5 NL at the end of the file.

        vim-6.4 is doing the right thing, with -b. As you say, without it, there is one NL at the end.

        • Note that eol has to be reset and binary has to be set.

          Vim 7 is working correctly here. Are you sure it’s not some global or filetype plugin or something screwing you up? What happens if you pass “-u NONE”?

          • Aha! That's it. It must be my crufty old vim-6 vintage vimrc file.

            Because vim -u NONE -b and setting noeol DOESN'T add the last NL with vim-7.

            I failed to realize my vimrc had led me astray just a few weeks ago.

            I set runtimepath in it. I can remember that was the cause of the problem then. But I can't remember what the problem itself was.