Emmet support

[Dan Eveland]

Hi,

Love BBedit. Been using for way too many years. Just upgraded to 11. I'll mention now that BBedit is one of only half-a-dozen apps on my Mac that is not from the app store, and is the only one in that category I don't mind paying for upgrades on.

Is there any way to get emmet functionality into BBedit? Is it already there and I am just not seeing it? There is a nice plugin for TextMate, but I am trying to focus on one singular text editor instead of having 4 installed all the time.

Thanks!

http://emmet.io

[Rich Siegel]

On Monday, October 27, 2014, Dan Eveland <deve...@gmail.com> wrote:

>Is there any way to get emmet functionality into BBedit?

You'll have to ask the Emmet implementors to do it. They will
tell you in reply that BBEdit doesn't support the plug-in
features that they need, to which I say that they should be
encouraged to look at the dialog front-ends for text filters
that got introduced in 11.0 (and you can point them here:
<http://www.barebones.com/support/technotes/filter-dialogs.html>).
If they want to make an effort to work with what the app has to
offer, we are happy to answer any specific questions they may
have. :-)

R.
--
Rich Siegel Bare Bones Software, Inc.
<sie...@barebones.com> <http://www.barebones.com/>

Someday I'll look back on all this and laugh... until they
sedate me.

[Maarten Sneep]

Hi,

> On 27 Oct 2014, at 21:12, Rich Siegel <sie...@barebones.com> wrote:
>
> You'll have to ask the Emmet implementors to do it. They will tell you in reply that BBEdit doesn't support the plug-in features that they need, to which I say that they should be encouraged to look at the dialog front-ends for text filters that got introduced in 11.0 (and you can point them here: <http://www.barebones.com/support/technotes/filter-dialogs.html>). If they want to make an effort to work with what the app has to offer, we are happy to answer any specific questions they may have. :-)

I have a question. Just for future reference I’m trying the instructions, you never know when this may prove useful (my latex tools could use an update…)

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’.

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? Adding the quoting would be nice as a future addition. (I was trying to answer these questions, but alas).

Thanks,

Maarten

[Rich Siegel]

On Tuesday, October 28, 2014, Maarten Sneep

<maarte...@xs4all.nl> 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.

>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.

>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. :-)

[Maarten Sneep]

> On 28 Oct 2014, at 15:51, Rich Siegel <sie...@barebones.com> wrote:
>
> On Tuesday, October 28, 2014, Maarten Sneep <maarte...@xs4all.nl> 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

[Kendall Conrad]

Before it was Emmet, it was Zen Coding. I made some scripts a few years back that implemented a portion of the features for TextWrangler and BBEdit. I haven't tried it on newer versions of BBEdit, but it likely still works. I only use TextWrangler these days so can't try out the filter dialogs that Rich pointed to. Hopefully the scripts can help you out though, but I have no current intentions to update them.

http://www.angelwatt.com/coding/zen-coding_bbedit.php

-Kendall

[Rick Yentzer]

Hey Maarten, 

I was wondering if you had any luck with this? 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

[Maarten Sneep]

Hi,

> On 17 Mar 2016, at 01:29, Rick Yentzer <ryen...@gmail.com> 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

> --
> This is the BBEdit Talk public discussion group. If you have a
> feature request or would like to report a problem, please email
> "sup...@barebones.com" 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 bbedit+un...@googlegroups.com.
> To post to this group, send email to bbe...@googlegroups.com.