Hi, > On 17 Mar 2016, at 01:29, Rick Yentzer <[email protected]> wrote: > > Hey Maarten, > > I was wondering if you had any luck with this?
The short version: no, and to be honest: I don’t quite remember the context of the conversation. Best, Maarten > I've used BBEdit for years and at my current job I use and IDE with Emmet. > Emmet is so ingrained in my workflow that it's hard to work around without a > mental reset, and I want to go back to just BBEdit. > > I've thought about porting some of Emmet's features to TextExpander but I > would lose some of it features, but I could live with that. > > I'll be reading up on the article Rich posted. > > Thanks, > Rick > > > On Tuesday, October 28, 2014 at 1:24:23 PM UTC-4, Maarten Sneep wrote: > > > On 28 Oct 2014, at 15:51, Rich Siegel <[email protected]> wrote: > > > > On Tuesday, October 28, 2014, Maarten Sneep <[email protected]> wrote: > > > >> The user interface in Xcode 6 is shuffled around enough so that I > >> can’t seem to find how to add a referencing outlet to the window. I’m > >> struggling at the step “The window should have its delegate and window > >> properties both bound to the File's Owner”, as it seems I can’t add a > >> referencing outlet for ‘window’. > > > > If you make the file's owner an NSWindowController, you should then be able > > to add a binding to the "window" property in the Outlets section. > > Thanks, that sentence is a helpful addition on the instruction page. > > >> The argument behaviour handling is nice, however, I wonder what > >> “String values (including file name paths) are not escaped or quoted > >> in any way” means in practice. How do you call the script internally? > >> Do string arguments with spaces end up in separate arguments from the > >> point of view of the script? > > > > No; each argument is an element of $ARGV, so the absence of quoting means > > simply that spaces and other such are unescaped. > > OK, this is probably what I would expect, but I’ll check. > > >> Adding the quoting would be nice as a future addition. (I was trying > >> to answer these questions, but alas). > > > > If it proves to be necessary for working functionality, I'll certainly > > consider it; but I'm trying not to add complexity in advance of > > demonstrated need. :-) > > With this information I can try it myself and see what happens. That’ll make > my needs more clear. > > One argument form that may be missing is a command mode, like the update in > ‘hg update’. The argument form for this would be just ‘value’. This would be > useful in combination with a popup menu. > > It would be nice to have an example to play with. > > Best, > > Maarten > > -- > This is the BBEdit Talk public discussion group. If you have a > feature request or would like to report a problem, please email > "[email protected]" rather than posting to the group. > Follow @bbedit on Twitter: <http://www.twitter.com/bbedit> > > --- > You received this message because you are subscribed to the Google Groups > "BBEdit Talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. -- This is the BBEdit Talk public discussion group. If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit> --- You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected].
