Loading ...
Sorry, an error occurred while loading the content.

134548Re: New line not recognized

Expand Messages
  • Christian Brabandt
    Nov 17, 2012
      Hi Tony!

      On Sa, 17 Nov 2012, Tony Mechelynck wrote:

      > On 17/11/12 09:00, jeroen wrote:
      > >On Friday, November 16, 2012 5:09:19 PM UTC+1, Marco wrote:
      > >>2012-11-16 Ben Fritz:
      > >>
      > >>
      > >>
      > >>>On Friday, November 16, 2012 9:55:10 AM UTC-6, Marco wrote:
      > >>
      > >>>>
      > >>
      > >>>>>My Windows GVim opened the file exactly as you described: one long line.
      > >>
      > >>>>>However, by using ":e ++ff=mac" (again, no quotes) I was able to reload the
      > >>
      > >>>>>file correctly.
      > >>
      > >>>>
      > >>
      > >>>>Thanks a lot, that works. Can I automate this somehow, so that vim
      > >>
      > >>>>opens <CR> (mac) files automatically with the ff=mac setting?
      > >>
      > >>>>
      > >>
      > >>>
      > >>
      > >>>:help 'fileformats' (note the s at the end).
      > >>
      > >>
      > >>
      > >>Thanks
      > >>
      > >>
      > >>
      > >> set fileformats=unix,dos,mac
      > >>
      > >>
      > >>
      > >>did the trick.
      > >>
      > >Is there any reason why this is not the default on unix?
      > >
      > >Jeroen
      > >
      > I'm not sure, but on Unix (well, on Linux) I have occasionally met
      > files which had a lot of lone carriage-returns and yet weren't Mac
      > files. This happens for instance when logging the stdout of a
      > console program which displays a text-mode "progess bar" by using a
      > CR to go to the left margin without advancing to the next line, in
      > order to overwrite the line just written. ISTR that rsync used to do
      > that (when I used it to keep my Vim source in sync before there was
      > a Mercurial repository), and maybe Mercurial (with the "progress"
      > extension), or the command-line "ftp" utility, do too. In that case
      > you don't want to break the line at a lone CR but you may want to
      > delete everything that precedes a CR which is not at the end of a
      > line (CR at the end of a line, i.e. followed by a line-feed
      > character, can be taken care of by reading the file with ++ff=dos).

      Sure enough, but that wouldn't have triggered Vim to set the fileformat
      to mac. As long there are some newlines in there, you would be safe.

      regards,
      Christian
      --

      --
      You received this message from the "vim_use" 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
    • Show all 17 messages in this topic