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

Fwd: Patch 7.3.191

Expand Messages
  • Benjamin Fritz
    Try three, after sending subscribe email. ... From: Benjamin Fritz Date: Thu, May 19, 2011 at 1:27 PM Subject: Re: Patch 7.3.191 To:
    Message 1 of 1 , May 19 7:28 PM
    • 0 Attachment
      Try three, after sending subscribe email.


      ---------- Forwarded message ----------
      From: Benjamin Fritz <fritzophrenic@...>
      Date: Thu, May 19, 2011 at 1:27 PM
      Subject: Re: Patch 7.3.191
      To: Bram Moolenaar <Bram@...>
      Cc: vim_dev <vim_dev@...>, vim_mac@...


      On Thu, May 19, 2011 at 11:40 AM, Bram Moolenaar <Bram@...> wrote:
      >> I wonder, if we might re-use this option to implement a similar
      >> extended attribute on Mac OS? See the following tip about saving the
      >> encoding information with the file, in the com.apple.TextEncoding
      >> extended attribute. I have no real idea how this stuff works (a google
      >> search didn't turn up very much of use) but it looks like something
      >> very useful which Vim could do if we can figure out how it is supposed
      >> to work. There are probably other extended attributes which might be
      >> more appropriate than the encoding, but I don't think encoding is that
      >> far off the intent of this option. Maybe, though, it's better to just
      >> do it in an autocmd like in the tip below:
      >>
      >> http://vim.wikia.com/wiki/Display_UTF-8_characters_in_Mac_Quicklook
      >
      > Is this actually being used and widely supported?
      >
      >

      That, I don't know. I have never had and probably never will have a
      Mac. I don't even really know which extended attributes there are or
      are commonly used. If there is one for file type, that would probably
      be a better thing to use for a resurrected osfiletype option. The
      specific one mentioned in the tip could conceiveably be used for
      encoding detection, and it would make sense to set it when writing,
      but it can readily be done in vimscript for now. I wish I could find
      documentation of the valid values, etc. I suspect most IANA encoding
      names should work, but I have no idea what the magic number used in
      the tip is for, and I really have no first-hand knowledge of any of
      this. From the little I could find, extended attributes in general
      should allow storing any useful information about the file to
      unambiguously determine file type, file encoding, and possibly other
      things as well. But I have no idea whether there are any widely-used
      standard values.

      --
      You received this message from the "vim_mac" 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
    Your message has been successfully submitted and would be delivered to recipients shortly.