Re: Edit Markup giving me an error

[Tom Robinson]

You should contact support — see the footer :]


> On 2018-01-22, at 07:24, Gerald Davenport  wrote:
> 
> Hi all. I have procrastinated enough, I am ready to move away from BBEdit 
> 8.7.2 and upgrade, but I have some issue with the trial version.
> 
> 12.0.2. running on an iMac with 10.13.2 iMac (27-inch, Mid 2011), maxed out 
> on ram.
> 
> Whenever i right click and want to Edit Markup I get the error attached as an 
> image
> 
> This operation couldn't be completed, because an error occurred.
> application error code: 11104
> 
> Interestingly enough, when I use the keyboard combination of command+M the 
> edit markup window works. and by the way it is far better than the 8.7.2 
> version.
> 
> So, it still works, but not with the right-click accessing the submenu.
> 
> Still buying the upgrade.
> - gerald
> 
> -- 
> This is the BBEdit Talk public discussion group. If you have a 
> feature request or would like to report a problem, please email
> "supp...@barebones.com" rather than posting to the group.
> Follow @bbedit on Twitter: 

-- 
This is the BBEdit Talk public discussion group. If you have a 
feature request or would like to report a problem, please email
"supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: 
--- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to bbedit@googlegroups.com.
Visit this group at https://groups.google.com/group/bbedit.

Re: Search, start at top and other things

[Bernardo]

Thanks John.
This version works :)

property startAtTop : true
property wrapAround : false
property caseSensitive : false
property matchWords : false
-

tell application "BBEdit"
- set prev search string
set prevSearchString to current search strings
try -- prev search string not always exists
set prevSearchString to search string of prevSearchString
on error
set prevSearchString to ""
end try
 perform search
set theChoice to display dialog "Search current document for:" default 
answer prevSearchString
if button returned of theChoice is "OK" then
set searchOpt to {starting at top:startAtTop, wrap around:wrapAround
, backwards:false, case sensitive:caseSensitive, match words:matchWords}
tell window 1
set findRes to find text returned of theChoice options 
searchOpt with selecting match
if findRes's found is false then beep
--set search string of current search strings to findRes -- 
seems useless
end tell
end if
end tell



-- 
This is the BBEdit Talk public discussion group. If you have a 
feature request or would like to report a problem, please email
"supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: 
--- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to bbedit@googlegroups.com.
Visit this group at https://groups.google.com/group/bbedit.

Re: Search, start at top and other things

[John Muccigrosso]

On Monday, January 22, 2018 at 9:34:40 AM UTC-5, Bernardo wrote:
>
> Thanks for your reply, John.
> Unfortunately, Applescript editor complains about an expected end of line 
> on the word "search" at the first line... I don't know why.
>
>>
>> *set* PREV_SEARCH_STRING *to* current search strings
>>
>>*set* PREV_SEARCH_STRING *to* search string *of* 
>> PREV_SEARCH_STRING
>>
>>
>>
Me either. It could be just a weird copy-paste thing. Try typing it in by 
hand, or maybe it's the more recent version of BBEdit? For that, use 
command-shift-O to open BBEdit's dictionary in the script editor and make 
sure those properties are still there. Meanwhile, this works for me:

*tell* *application* "BBEdit"

   *set* PREV_SEARCH_STRING *to* current search strings

   

   *set* PREV_SEARCH_STRING *to* search string *of* PREV_SEARCH_STRING

   

   *set* theChoice *to* *display dialog* "Search current document for:" 
default answer PREV_SEARCH_STRING

   

   *if* button returned *of* theChoice *is* "OK" *then*

   *set* searchOpt *to* {starting at top:*true*}

   *tell* *window* 1

   *set* findRes *to* *find* text returned *of* 
theChoice options searchOpt *with* selecting match

   *if* findRes's found *is* *false* *then* *beep*

   *set* search string *of* current search strings *to* 
findRes

   *end* *tell*

   *end* *if*

*end* *tell*


For some reason BBEdit doesn't remember the search string if you change it 
in the dialog.


-- 
This is the BBEdit Talk public discussion group. If you have a 
feature request or would like to report a problem, please email
"supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: 
--- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to bbedit@googlegroups.com.
Visit this group at https://groups.google.com/group/bbedit.

Re: Search, start at top and other things

[Bernardo]

Thanks for your reply, John.
Unfortunately, Applescript editor complains about an expected end of line 
on the word "search" at the first line... I don't know why.

>
> *set* PREV_SEARCH_STRING *to* current search strings
>
>*set* PREV_SEARCH_STRING *to* search string *of* PREV_SEARCH_STRING
>
>
>

-- 
This is the BBEdit Talk public discussion group. If you have a 
feature request or would like to report a problem, please email
"supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: 
--- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to bbedit@googlegroups.com.
Visit this group at https://groups.google.com/group/bbedit.

Edit Markup giving me an error

[Gerald Davenport]

Hi all. I have procrastinated enough, I am ready to move away from BBEdit 
8.7.2 and upgrade, but I have some issue with the trial version.

12.0.2. running on an iMac with 10.13.2 iMac (27-inch, Mid 2011), maxed out 
on ram.

Whenever i right click and want to Edit Markup I get the error attached as 
an image

*This operation couldn't be completed, because an error occurred.*
application error code: 11104

Interestingly enough, when I use the keyboard combination of command+M the 
edit markup window works. and by the way it is far better than the 8.7.2 
version.

So, it still works, but not with the right-click accessing the submenu.

Still buying the upgrade.
- gerald

-- 
This is the BBEdit Talk public discussion group. If you have a 
feature request or would like to report a problem, please email
"supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: 
--- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to bbedit@googlegroups.com.
Visit this group at https://groups.google.com/group/bbedit.

Re: HTML5 support

[Jean-Christophe Helary]

> On Jan 22, 2018, at 22:46, Greg Raven  wrote:
> 
> Third, I'm not finding either translate or fade as HTML5 elements, and they 
> don't even sound like elements, IMHO. Are you certain they are not attributes 
> or CSS?

translate is an attribute:
https://www.w3.org/International/questions/qa-translate-flag

There is a ling between the translate attribute and the ITS specification

"The ITS 2.0 specification has a normative dependency on the HTML5 
specification: it relies on the HTML5 Translate attribute. By publishing this 
Recommendation, W3C expects that the functionality specified in this ITS 2.0 
Recommendation will not be affected by changes to HTML5 as that specification 
proceeds to Recommendation."

https://www.w3.org/TR/its20/#html5-global-approach

It's a fascinating area of work, even if slightly off-topic in this thread :)


Jean-Christophe Helary
---
http://mac4translators.blogspot.com @brandelune


-- 
This is the BBEdit Talk public discussion group. If you have a 
feature request or would like to report a problem, please email
"supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: 
--- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to bbedit@googlegroups.com.
Visit this group at https://groups.google.com/group/bbedit.

Re: HTML5 support

[Greg Raven]

First, not every possibility is in the palette. Some tags need to invoke 
using other means.

Second, canvas works in my version of BBEdit. BBEdit not only recognizes it 
as a tag in Edit Markup ..., the BBEdit syntax checker also recognizes it 
as valid.

Third, I'm not finding either translate or fade as HTML5 elements, and they 
don't even sound like elements, IMHO. Are you certain they are not 
attributes or CSS?

The original post made it sound as if there was no HTML5 support in BBEdit, 
which is incorrect.

Perhaps you can provide an example? "Etc." isn't very helpful.

On Monday, January 22, 2018 at 1:16:14 AM UTC-8, jgill wrote:
>
> Canvas, translate, fade etc. etc.
>
>
> On Thursday, January 18, 2018 at 5:23:09 AM UTC, Robert wrote:
>>
>> I was just creating some quick web pages and noticed that the "HTML 
>> Tools" palette doesn't seem to have HTML5 support. Is that planned?
>>
>> -- 
>> Bob
>>
>

-- 
This is the BBEdit Talk public discussion group. If you have a 
feature request or would like to report a problem, please email
"supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: 
--- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to bbedit@googlegroups.com.
Visit this group at https://groups.google.com/group/bbedit.

Re: HTML5 support

[jgill]

Canvas, translate, fade etc. etc.


On Thursday, January 18, 2018 at 5:23:09 AM UTC, Robert wrote:
>
> I was just creating some quick web pages and noticed that the "HTML Tools" 
> palette doesn't seem to have HTML5 support. Is that planned?
>
> -- 
> Bob
>

-- 
This is the BBEdit Talk public discussion group. If you have a 
feature request or would like to report a problem, please email
"supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: 
--- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to bbedit@googlegroups.com.
Visit this group at https://groups.google.com/group/bbedit.