On Sat, Oct 2, 2010 at 10:01 AM, björn <[email protected]> wrote:
> On 2 October 2010 03:26, Alec Thomas <[email protected]> wrote: > > On Sep 3, 5:12 am, David Salgado <[email protected]> wrote: > >> > >> I think I'll leave things as they are; if more people complain about > >> it I'll start thinking about a better solution. (It's only a guess, > >> but I think most people do want the pwd to be set to the first file > >> they open.) > > > > Hi Björn, > > > > There's a long discussion about this issue on this PeepOpen bug > > tracker issue: > http://github.com/topfunky/PeepOpen-Issues/issues#issue/62 > > > > PeepOpen is an external application launched from vim. It offers up a > > nice efficient file dialog. Once a file is selected PeepOpen tells > > MacVim to open the file, which is where it hits this issue. > > > > For reference, here's how I typically use MacVim in order of > > frequency: > > > > 1. Open it from the dock, then ":cd <project-root>", then use PeepOpen > > to open various files under the project root. > > 2. Cd into the project directory from the command line then run mvim > > (though since this change I now run "mvim ."). > > 3. Open MacVim by clicking or right-clicking on files (typically > > source I've downloaded to check out) in Finder. > > > > Here are some suggestions that might help (any of which would solve > > this issue for PeepOpen users specifically): > > > > 1. Disable the feature as soon as any command is typed into MacVim at > > all. > > 2. Disable the feature if the user launches MacVim via mvim. > > 3. Add a MacVim-specific option to disable the feature. > > I see that something has to change...but I'm still not sure how. The > current behavior is confusing to say the least -- when I change it I > want it to be completely obvious what is going on. I'd rather avoid > introducing another option for this. > > Under what circumstances _should_ the pwd be set? > > Well, if new files open in a new window then I guess it should always > be set when opening a file (?), so the question only really applies to > when you've set MacVim to open files in the "current" window. Maybe > with this option set the pwd should never be touched? At least this > is consistent (I think your suggestions 1 & 2 may lead to some > confusion however). > > Does anybody have comments on this (please make yourselves heard)? > > Let me rephrase this slightly: is there anybody out there who has got > MacVim set to open files in the "current" window and who wants the pwd > to be set when they open a new file? (If so, when?) > I imagine those people are already the type of people who change directories on BufEnter (I know at least one). My $.04 (stupid currency devaluing): Personally I never switch directories, but that's because I almost always run vim from the command line if I'm in a situation where I'd want to (specifically: I do lots of coding on linux. I use the command line version of vim a lot. In MacVim, I rarely care what directory I'm in since it's rare that I have a tree of files that I need to navigate.. if the file has siblings, I'll just automatically use %:h/ to get to them). I think the proposed solution is probably the best one. It doesn't bother users like me (who don't care what pwd is), and it shouldn't bother the BufEnter directory changers, since BufEnter should still fire (after you've modified the pwd), and you're probably setting it to what they want anyway. > > > PS. Thanks for your work on MacVim, it is fantastic :) > > I'm glad you like it! > > > Björn > > -- > 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 > -- 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
