On 26-Jan-2010, at 12:29, Tim Gray wrote: > On Tue 26, Jan'10 at 12:09 PM -0700, LuKreme wrote: >> Please don't restrict it to only GUI AppleEvent editors. ANY editor that >> properly supports being an external editor (vim, nano, nvi, emacs, etc) >> should be usable. > > That would be cool, but I've never found a legit method for open-ended > communication to interactive CLI programs that get called from a GUI program.
Erm, not, that's not how it works at ALL because that would be, well, that would be all sorts of bad. Here's how I use BBEdit as an external editor for slrn: set editor_command "bbedit -w --resume +%d '%s'" -w tells the bbedit CLI tool to wait until BBEdit has closed the file. the --resume tells the CLI tool to put whatever application was in the foreground before back in the foreground. In slrn, this is the Terminal, which means that when I post, I get a BBEdit window and when I close that window, I am back at my message list in slrn. This is, effectively, how good shell editors work, which is why you can set your EDITOR environment to most any editor you want (including bbedit) and it just works. -- 'My strength is like the strength of ten because my heart is pure,' said Carrot. 'Really? Well, there's eleven of them.' --Jingo _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
