Cyberduck and MacVim.app
newbie
this 2 lines in your terminal:
$ defaults write ch.sudo.cyberduck editor.bundleIdentifier
org.vim.MacVim
$ defaults write ch.sudo.cyberduck editor.name MacVim
anmar
list of editor
anmar
anmar
editors in their list of external editors.
Here it is: <http://trac.cyberduck.ch/ticket/1322>
I am no developer so I don't know how to go about it but it would be
great if one of you adds MacVim then creates a patch and attaches it
to the ticket to speed it up a little bit.
anmar
On Nov 1, 8:57 am, newbie <djta...@gmail.com> wrote:
anmar
I just heard that cyberduck only supports editors with ODB. I am not
100% sure if MacVim supports it so can you please shed some light on
this subject so I can push this issue forward with CyberDuck
developers.
The ODB information page is at <http://www.barebones.com/support/
develop/odbsuite.shtml>
anmar
Nico Weber
> I just heard that cyberduck only supports editors with ODB. I am not
> 100% sure if MacVim supports it so can you please shed some light on
> this subject so I can push this issue forward with CyberDuck
> developers.
there is a ODB patch for Carbon vim available at http://wiki.macvim.org/wiki/VimPatches/ODBEditor
(but the wiki is still down. Panos?). This patch has not yet been
ported to MacVim as far as I know.
Nico
björn
I have started looking into adding ODB support for MacVim so it will
be there soon enough. ;-)
/Björn
anmar
with Cyberduck.
anmar
On Nov 3, 4:26 am, "björn" <bjorn.winck...@gmail.com> wrote:
> On 03/11/2007, Nico Weber <nicolaswe...@gmx.de> wrote:
>
>
>
> > Hi,
>
> > > I just heard that cyberduck only supports editors with ODB. I am not
> > > 100% sure if MacVim supports it so can you please shed some light on
> > > this subject so I can push this issue forward with CyberDuck
> > > developers.
>
> > there is a ODB patch for Carbon vim available athttp://wiki.macvim.org/wiki/VimPatches/ODBEditor
Steve Huff
>
> I have started looking into adding ODB support for MacVim so it will
> be there soon enough. ;-)
excellent!
another app that uses ODB for external editor support is the Saft
extension for Safari (http://haoli.dnsalias.com/saft/). at present
MacVim opens correctly when called from Saft, but when MacVim saves
the file or exits it does not correctly send a notification back to
Saft.
i look forward to the implementation of this feature. :)
-steve
björn
I have finished the implementation of ODB Editor support. Grab the
latest version from Git and compile to try it out. I will be
interested to hear how it works because I myself have no programs that
have ODB support to test it with (I've done some basic testing with
the 'odbedit' command line program).
It is a fairly complete implementation. At the moment I do not
display the 'keyFileCustomPath' [1] string, but I am guessing it
should be used as the window title if the external program passes it.
Does anybody have any suggestions as to what I should do with this
parameter?
Xcode support is next...but to be quite honest, Xcode support will
never be good for much since the Xcode protocol is so lame.
/Björn
foosh
> I have finished the implementation of ODB Editor support. Grab the
> latest version from Git and compile to try it out.
specifically for ODB support?
Adam Mercer
> Do you have a diff available displaying what changes were made
> specifically for ODB support?
This is the appropriate commit from the git repo, is this what you're after?
<http://repo.or.cz/w/MacVim.git?a=commitdiff;h=56d8b36c762c733f37b0edb0009b284e6a255a4e>
Cheers
Adam
foosh
> This is the appropriate commit from the git repo, is this what you're after?
Nico Weber
> you're after?
>
> <http://repo.or.cz/w/MacVim.git?a=commitdiff;h=56d8b36c762c733f37b0edb0009b284e6a255a4e
> >
Bjorn, you change the bundle identifier from org.vim.MacVim to
org.vim.MacVim-odb . I guess that was not intentional?
Using the bundle identifier as IPC port name causes all kinds of
problems. Perhaps we could use the alias id of the main bundle? This
should stay constant even if the app is used and is different for
different MacVim instances. This way, you could run a "normal" MacVim
and a developement MacVim in parallel with no hassle at all.
Nico
Nico Weber
> latest version from Git and compile to try it out. I will be
> interested to hear how it works because I myself have no programs that
> have ODB support to test it with (I've done some basic testing with
> the 'odbedit' command line program).
I would have tested it with Cyberduck, but they hardcoded the editors
they support ( http://trac.cyberduck.ch/browser/trunk/source/ch/cyberduck/ui/cocoa/odb/Editor.java
). There's a bug about adding MacVim ( http://trac.cyberduck.ch/ticket/1322
), but this probably can't be fixed until there's a build of MacVim
that supports ODB :-P
Seems to work fine in Transmit.
> It is a fairly complete implementation. At the moment I do not
> display the 'keyFileCustomPath' [1] string, but I am guessing it
> should be used as the window title if the external program passes it.
> Does anybody have any suggestions as to what I should do with this
> parameter?
This should probably be used as file name in the title. Perhaps add a
possibility to have a "customPath empty ? realPath : customPath"
option to titlestr (and make it the default). Right now, MacVim
displays the path to some temporary file for ODB edited files.
> Xcode support is next...but to be quite honest, Xcode support will
> never be good for much since the Xcode protocol is so lame.
What does "Xcode support" mean? I'm currently using MacVim as my
editor in Xcode and it already does what I'd expect it to do (but it'd
be nice if I could click on compile errors in xcode and have MacVim
jump to the offending line. Is this possible with what you're planning
to do?)
Nico
Tim Allen
> > It is a fairly complete implementation. At the moment I do not
> > display the 'keyFileCustomPath' [1] string, but I am guessing it
> > should be used as the window title if the external program passes it.
> > Does anybody have any suggestions as to what I should do with this
> > parameter?
>
> This should probably be used as file name in the title. Perhaps add a
> possibility to have a "customPath empty ? realPath : customPath"
> option to titlestr (and make it the default). Right now, MacVim
> displays the path to some temporary file for ODB edited files.
:e http://slashdot.org/
...then ^G lists the filename as "http://slashdot.org/" even though
you're really editing a temporary file on the local disk. Could ODB
use a similar mechanism?
Ben Schmidt
Mmm. I personally think that'd be the best solution. Give the 'filename' an odb:
prefix like a URL scheme and intercept it with autocommands to do the tempfile
writing/calling whatever stuff needs to be called to report back to the caller.
Ben.
Send instant messages to your online friends http://au.messenger.yahoo.com
björn
>
> > This is the appropriate commit from the git repo, is this what
> > you're after?
> >
> > <http://repo.or.cz/w/MacVim.git?a=commitdiff;h=56d8b36c762c733f37b0edb0009b284e6a255a4e
> > >
>
> Bjorn, you change the bundle identifier from org.vim.MacVim to
> org.vim.MacVim-odb . I guess that was not intentional?
Nicely spotted. It was indeed unintentional but I fixed it before
pushing to the public repo (the commit after has the fix).
Still...thanks.
> Using the bundle identifier as IPC port name causes all kinds of
> problems. Perhaps we could use the alias id of the main bundle? This
> should stay constant even if the app is used and is different for
> different MacVim instances. This way, you could run a "normal" MacVim
> and a developement MacVim in parallel with no hassle at all.
I agree that using the bundle identifier for the named port is a bit
awkward (but only for developers, which is why I didn't think it too
much of an evil). I considered using the path of the main executable
as the ID, but apparently in Mac OS X land the user is supposed to be
able to move the app bundle while the program is running (!), so I did
not dare to use that. What is the "alias id" you are talking
about...is it something that cannot change while the app is running?
/Björn
björn
> > latest version from Git and compile to try it out. I will be
> > interested to hear how it works because I myself have no programs that
> > have ODB support to test it with (I've done some basic testing with
> > the 'odbedit' command line program).
>
> I would have tested it with Cyberduck, but they hardcoded the editors
> they support ( http://trac.cyberduck.ch/browser/trunk/source/ch/cyberduck/ui/cocoa/odb/Editor.java
> ). There's a bug about adding MacVim ( http://trac.cyberduck.ch/ticket/1322
> ), but this probably can't be fixed until there's a build of MacVim
> that supports ODB :-P
>
> Seems to work fine in Transmit.
Good to know.
> > It is a fairly complete implementation. At the moment I do not
> > display the 'keyFileCustomPath' [1] string, but I am guessing it
> > should be used as the window title if the external program passes it.
> > Does anybody have any suggestions as to what I should do with this
> > parameter?
>
> This should probably be used as file name in the title. Perhaps add a
> possibility to have a "customPath empty ? realPath : customPath"
> option to titlestr (and make it the default). Right now, MacVim
> displays the path to some temporary file for ODB edited files.
That's what I was thinking too...I'd better get an ODB aware program
to test it out with though, to see that it looks ok.
> > Xcode support is next...but to be quite honest, Xcode support will
> > never be good for much since the Xcode protocol is so lame.
>
> What does "Xcode support" mean? I'm currently using MacVim as my
> editor in Xcode and it already does what I'd expect it to do (but it'd
> be nice if I could click on compile errors in xcode and have MacVim
> jump to the offending line. Is this possible with what you're planning
> to do?)
Xcode supports a subset of the CodeWarrior protocol for external
editors (see [1]). It boils down to two Apple events:
1) when opening files Xcode passes the line number/selection range
(what you mentioned above)
2) when the user hits Cmd-B in Xcode (for example), it sends a "MOD "
apple event to the editor (i.e. MacVim) asking for files that are
modified. I'm not sure what this event is supposed to do, but check
[1]...it seems like Xcode presents a dialog to save the unsaved files,
but how this is supposed to work with Vim I do not know.
I have already done item (1) but I am sort struggling with the second item.
/Björn
björn
> On 28/11/2007, Nico Weber <nicola...@gmx.de> wrote:
> >
> > > It is a fairly complete implementation. At the moment I do not
> > > display the 'keyFileCustomPath' [1] string, but I am guessing it
> > > should be used as the window title if the external program passes it.
> > > Does anybody have any suggestions as to what I should do with this
> > > parameter?
> >
> > This should probably be used as file name in the title. Perhaps add a
> > possibility to have a "customPath empty ? realPath : customPath"
> > option to titlestr (and make it the default). Right now, MacVim
> > displays the path to some temporary file for ODB edited files.
>
> That's what I was thinking too...I'd better get an ODB aware program
> to test it out with though, to see that it looks ok.
Does anybody know a ODB aware program that actually passes the "custom
path" parameter with the "ODB open" event? I tried Cyberduck but it
did not pass it; I also tried a demo version of Transmit but it
doesn't even seem to support ODB! Any other suggestions?
/Björn
nicola...@gmx.de
> path" parameter with the "ODBopen" event? I tried Cyberduck but it
> doesn't even seem to supportODB! Any other suggestions?
There's also the "Edit in vim" input manager: http://slashpunt.org/vim/index.php?n=Main.Download
I didn't try it, though.
Nico
björn
Thanks for the link...however I'd like to know a program that somebody
knows for sure uses the 'custom path' parameter (this is an optional
parameter in the odb open event). I was hoping that somebody who
actually uses odb on this list would know more...
I made a brief attempt at getting the "Edit in TextMate" input manager
to work with MacVim but no luck yet...I might give it another go later
(unless somebody else would like to help out and fix this...get the
source from [1])....it would be nice to have.
/Björn
[1] http://anon:an...@macromates.com/svn/Bundles/trunk/Tools/Edit%20in%20TextMate/
anmar
I just got an e-mail from cyberDuck bug tracker. MacVim is now on the
list of supported editors. See Text below:
---- begin of paste ----
Changes (by dkocher):
* status: new => closed
* resolution: => fixed
* milestone: => 2.8.2
Comment:
As of r3331 we support MacVim if it has the bundle identifier
''org.slashpunt.vim''
------- end of paste ------
björn: do we have that bundle identifies in place ?
anmar
On Dec 3, 9:17 am, "björn" <bjorn.winck...@gmail.com> wrote:
>
>
>
> > > Does anybody know aODBaware program that actually passes the "custom
> > > doesn't even seem to supportODB! Any other suggestions?
>
> > Here's a list:http://wiki.macromates.com/Main/TextMateAwarePrograms
> > There's also the "Edit in vim" input manager:http://slashpunt.org/vim/index.php?n=Main.Download
> > I didn't try it, though.
>
> Thanks for the link...however I'd like to know a program that somebody
> knows for sure uses the 'custom path' parameter (this is an optional
> parameter in the odb open event). I was hoping that somebody who
> actually uses odb on this list would know more...
>
> I made a brief attempt at getting the "Edit in TextMate" input manager
> to work with MacVim but no luck yet...I might give it another go later
> (unless somebody else would like to help out and fix this...get the
> source from [1])....it would be nice to have.
>
> /Björn
>
björn
>
> Hello Guys:
>
> I just got an e-mail from cyberDuck bug tracker. MacVim is now on the
> list of supported editors. See Text below:
> ---- begin of paste ----
> Changes (by dkocher):
>
> * status: new => closed
> * resolution: => fixed
> * milestone: => 2.8.2
>
> Comment:
>
> As of r3331 we support MacVim if it has the bundle identifier
> ''org.slashpunt.vim''
> ------- end of paste ------
>
> björn: do we have that bundle identifies in place ?
That's no good. The bundle identifier for MacVim is org.vim.MacVim.
You better ask them to change that.
/Björn
anmar
Sure.. no worries. I will keep you up to date.
anmar
On Dec 6, 1:33 pm, "björn" <bjorn.winck...@gmail.com> wrote:
Bruno De Fraine
> There's also the "Edit in vim" input manager:http://slashpunt.org/vim/index.php?n=Main.Download
> I didn't try it, though.
For me this one works with MacVim 0712A and B. (Under Leopard, where
you have to install the Input Manager in the global /Library/
InputManagers, see http://blog.macromates.com/2007/inputmanagers-on-leopard/
)
As described on the download page, you have to configure your
particular ODBEditor (otherwise it defaults to Carbon Vim).
defaults write org.slashpunt.edit_in_odbeditor
ODBEditorBundleIdentifier org.vim.MacVim
defaults write org.slashpunt.edit_in_odbeditor ODBEditorName MacVim
Regards,
Bruno
björn
Ah, thanks for the tip...I never looked closely enough to see that it
can work with any ODB Editor. However, it does not work for me. I
get the same error as when I tried to compile the "Edit in TextMate"
Input Manager myself:
"Can't open input server /Library/InputManagers/Edit in ODBEditor.bundle"
Does anybody else have these problems? (I have a G4 with 10.4.11)
I first tried installing it under ~/Library/InputManagers (which is
supposed to work on Tiger, but didn't) and then under
/Library/InputManagers (following the instructions for Leopard, still
did not work). I also made sure there is only one copy of the input
manager on my hard drive and I logged in/out before trying to use it.
/Björn
travis
Did you do anything else other than doing the defaults commands
installing the Input Manager?
> > There's also the "Editin vim" input manager:http://slashpunt.org/vim/index.php?n=Main.Download
>
björn
>
> I installed it but I don't get the command in the Menu Bar --> Edit.
> Did you do anything else other than doing the defaults commands
> installing the Input Manager?
>
> > Hi,
> >
> > > There's also the "Editin vim" input manager:http://slashpunt.org/vim/index.php?n=Main.Download
> > > I didn't try it, though.
> >
> > For me this one works withMacVim0712A and B. (Under Leopard, where
> > you have to install the Input Manager in the global /Library/
> > InputManagers, seehttp://blog.macromates.com/2007/inputmanagers-on-leopard/
> > )
> >
> > As described on the download page, you have to configure your
> > particular ODBEditor (otherwise it defaults to Carbon Vim).
> >
> > defaults write org.slashpunt.edit_in_odbeditor
> > ODBEditorBundleIdentifier org.vim.MacVim
> > defaults write org.slashpunt.edit_in_odbeditor ODBEditorNameMacVim
Has anybody else, apart from Bruno, managed to get the above input
manager to work with MacVim? I am still unable to use it.
It would be good if some people on this list tried it out and let me
know if they could get it to work or not.
Thanks,
Björn
travis
installation and it worked!
"
(- This is a Leopard machine, AFAIK he had no Vims or input
managers installed.)
- Download the latest MacVim, we used snapshot 0712B. Install to
the /Applications directory. Open it.
- Download and mount the disk image from http://slashpunt.org/vim/index.php?n=Main.Download
- From the Terminal, do:
ODBEditorBundleIdentifier "org.vim.MacVim"
defaults write org.slashpunt.edit_in_odbeditor ODBEditorName
MacVim
sudo cp -pR "/Volumes/Vim/Edit in ODBEditor" /Library/
InputManagers
sudo chown -R root:admin /Library/InputManagers
- Start (or restart) the application where you want the Input
Manager, we used "TextEdit".
- We could now see (and use) the "Edit in MacVim" item in the
"Edit" menu. The original document is opened in a new window (e.g.
"VIM1"). Every time you :w from MacVim, the data is sent back to the
original application. When you :q, the original application regains
focus.
- Afterwards, I also tried the "Edit in MacVim" item when MacVim
is not yet opened. This works as well.
"
That's what he sent me, I tried it out with the latest build, and with
other InputManagers already installed so I think anyone who follows
these should get it to work.
On Jan 23, 2:15 pm, "björn" <bjorn.winck...@gmail.com> wrote:
dc...@mrjoy.com
website as of Sunday evening is slightly off. I too have been getting
the "Can't open input server /Library/InputManagers/Edit in
ODBEditor.bundle" errors.
The current documentation says:
>1. From the Terminal, do (the backslash indicates that the command you have to
> type continues on the next line):
> defaults write org.slashpunt.edit_in_odbeditor \
> ODBEditorBundleIdentifier "org.vim.MacVim"
> defaults write org.slashpunt.edit_in_odbeditor \
> ODBEditorName MacVim
> sudo mkdir /Library/InputManagers
> /Library/InputManagers
sudo cp -pR ~/"Desktop/ODBInputManager/Edit in ODBEditor" /Library/
InputManagers
the ~ needs to not be in "" to expand correctly.
Also, to be clear, the .bundle should NOT be directly in the
InputManagers directory.
The tilde expansion failed for me, so when I re-ran it, I used tab-
complete, which stuck a / on the tail of the "Edit in ODBEditor" This
copies the contents of
Edit in ODBEditor" without the directory itself, and you get
the .bundle in /Library/InputMethods. You want to end up with
something like this tree:
/Library/InputManagers
/Library/InputManagers/.DS_Store
/Library/InputManagers/Edit In ODBEditor
/Library/InputManagers/Edit In ODBEditor/Edit in ODBEditor.bundle
/Library/InputManagers/Edit In ODBEditor/Edit in ODBEditor.bundle/
Contents
/Library/InputManagers/Edit In ODBEditor/Edit in ODBEditor.bundle/
Contents/Info.plist
/Library/InputManagers/Edit In ODBEditor/Edit in ODBEditor.bundle/
Contents/MacOS
/Library/InputManagers/Edit In ODBEditor/Edit in ODBEditor.bundle/
Contents/MacOS/Edit in ODBEditor
/Library/InputManagers/Edit In ODBEditor/Edit in ODBEditor.bundle/
Contents/Resources
/Library/InputManagers/Edit In ODBEditor/Edit in ODBEditor.bundle/
Contents/Resources/English.lproj
/Library/InputManagers/Edit In ODBEditor/Edit in ODBEditor.bundle/
Contents/Resources/English.lproj/InfoPlist.strings
/Library/InputManagers/Edit In ODBEditor/Edit in ODBEditor.bundle/
Contents/Resources/url map.plist
/Library/InputManagers/Edit In ODBEditor/Info
björn
Thanks...I have updated the instructions to point out that it is very
important not to add that extra slash after the paths when copying
folders. (Also, see my reply to Ted's post.)
/Björn