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

11110Re: Disable "New Document Containing Selection" option when text is selected

Expand Messages
  • björn
    Dec 3, 2009
    • 0 Attachment
      2009/12/3 Carl Jacobsen:
      >
      > I notice two things, looking at the NSServices section of Info.plist...
      >
      > First, on Snow Leopard, the initial "MacVim/" part of the descriptions
      > doesn't come through, which makes the descriptions in the context menu
      > (only) confusing (in the Services menu, there's a little MacVim icon
      > in front of the name, and in Leopard's Services menu, the "MacVim/"
      > part turns into a nice submenu).  Perhaps MacVim should be incorporated
      > into the service names?  Something like changing the names:
      >
      >        MacVim/New Document Containing Selection
      >        MacVim/Open Selected File
      >        MacVim/New Document Here
      > to these:
      >        MacVim/New MacVim Document Containing Selection
      >        MacVim/Open Selected File with MacVim
      >        MacVim/New MacVim Document Here
      >
      > (leaving the "MacVim/" on the front so Leopard still gets a submenu
      > in Services; it seems to be harmlessly ignored in Snow Leopard).

      Good idea. I'll implement these changes.


      > Second, the "Open Selected File" and "New Document Here" services don't
      > show up in Snow Leopard (in my experience, at least).  I would dearly
      > love to be able to control-click in a Finder folder and choose "New
      > MacVim Document Here"...  Any chance of getting this working in Snow
      > Leopard?
      >
      > If it helps, the one example I have at hand of an app that *does* show
      > up in the context menu on Snow Leopard, when control-clicking in a
      > Finder window is EagleFiler.  Where MacVim has (roughly) this:
      >
      >        <key>NSRequiredContext</key>
      >        <dict>
      >                <key>NSTextContent</key>
      >                <string>FilePath</string>
      >        </dict>
      >        <key>NSSendTypes</key>
      >        <array>
      >                <string>NSStringPboardType</string>
      >        </array>
      >
      > EagleFiler appears to instead have this:
      >
      >        <key>NSRequiredContext</key>
      >        <dict>
      >        </dict>
      >        <key>NSSendTypes</key>
      >        <array>
      >                ...
      >                <string>NSFilenamesPboardType</string>
      >                ...
      >        </array>
      >
      > essentially not requiring a specific context, but instead expecting
      > a NSFilenamesPboardType type.

      I had a look at Mail.app and it does not specify NSRequiredContext at
      all (not even an empty dictionary). I'll fix this as well.

      Thanks for the suggestions!
      Björn

      --
      You received this message from the "vim_mac" maillist.
      For more information, visit http://www.vim.org/maillist.php
    • Show all 6 messages in this topic