What am I missing in BBEdit 10?
NotInUse
Mac OS 10.6.8 and Mac OS10.7 - tested both with BBEdit10.
First edit using BBEdit 10, happens to be a basic HTML file.
I can't seem to get any modal windows whatsoever. I can't drag and
drop images. The new popup tag editor is... well... 300% more work
than the previous modal windows of v9.6. Inserting images doesn't auto
insert dimensions or retain previous settings such as border or
alignment. Yes, I've used the Command and/or Option keys with
absolutely no results.
All the things I absolutely loved about editing HTML with BBEdit seem
to have vanished. Must I now type every single value needed
everywhere?
I'm hopeful that this is merely user error and I'm missing something
because right now... it's pretty apparent why the price was cut by
2/3rds for this version --- it's 1/3 as good as any previous version.
Please, please, PLEASE, enlighten me.
I have already searched the FAQ, the manual, and this group with
pretty much no results.
Thanks!
Robert Huttinger
--
You received this message because you are subscribed to the
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to bbe...@googlegroups.com
To unsubscribe from this group, send email to
bbedit+un...@googlegroups.com
For more options, visit this group at
<http://groups.google.com/group/bbedit?hl=en>
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>
NotInUse
entirely user error. And it may full well be. And I'll be the idiot
and kick myself accordingly.
It's not unreasonable to be unhappy that money was paid for a product
and the product does not perform the basic expected functions. I have
deadlines. I've sent an email to support before posting here..... no
clue when or if that will be answered.
I've been a BBEdit user since OS9. After over a decade of use to
launch a version and suddenly not have features is unsettling. Sorry
if I didn't bring flowers and candy to my post. I want what I paid for
to function. If it were not for older versions, I'd be much less
happy. Thankfully I can simply use v9.6 which does function.
Tell you what... you send me $40 and I'll send you an app.. that app
won't do much of anything, but at least you'll get something sitting
on your hard drive for you hard earned money.
On Jul 22, 7:32 am, Robert Huttinger <roberthuttin...@gmail.com>
wrote:
François Schiettecatte
1) You are crapping all over the software without asking specific questions about specific problems, hard to see that as anything but negative. If you have specific issues the people on this list are usually very willing to help. Many go above and beyond.
2) New releases are always difficult and I am sure the BB crew are snowed under with questions/bug reports/etc... Rich has said as much.
3) If you have deadlines what were you thinking doing a major upgrade in mid-stream? I always wait for downtime before upgrading anything in my critical path.
4) Every major upgrade of BBEdit has brought changes, some painful, most great. I know that because I have been using BBEdit since OS 7.
Again no affiliation with BB, except that we are both located on the same side of Boston (currently getting roasted!)
Cheers
François
> please email "sup...@barebones.com" rather than posting to the group.
NotInUse
sentences.
I've pointed out my issues and asked to be enlightened. Guess you
missed that completely.
As I posted.. I have several versions of the app and will revert for
use. But I don't like being charged for an app which is missing core
functionality. I don't think 90% of users would be happy with that.
And ever heard of beta testing? I realize new versions have bugs and
issues. But really.. come one.. huge issues like image insertion in
HTML files is not something that could be easily overlooked. It should
have been presented the first day of beta testing and should have
NEVER made it to a release candidate. I beta test for MAJOR software
companies. Have for many years.
You're being unrealistic.
On Jul 22, 7:55 am, François Schiettecatte <fschietteca...@gmail.com>
wrote:
NotInUse
dimensions or the fact that I can't drag and drop form anywhere.. i'm
all ears.
How about addressing the PROBLEM rather than telling me how I should
be posting???
Steve Kalkwarf
> Honestly, if you guys have a solution for no auto-insertion of image
> dimensions or the fact that I can't drag and drop form anywhere.. i'm
> all ears.
Critiquing our ability to write and test code isn't the best way to get help. Complaining that the software you failed to use the trial period for doesn't perform to your expectations seems a little silly, but since you're obviously an expert at beta testing, I'm probably wrong about that, too.
> How about addressing the PROBLEM rather than telling me how I should
> be posting???
As written, and tested during the beta cycle, dragging an image into an HTML document inserts complete and correct markup:
<img src="file://localhost/Users/kalkwarf/Pictures/Fabulous%20Dog.jpg" alt="Fabulous Dog.jpg" width="1280" height="960">
If you are seeing different results, there is either a bug in the software, or a mis-aligned expectation.
I would write to support, as I believe you said you had. When the folks answering questions get to your report, they'll probably ask questions, like what language the document is in, and what the full path to the the image is, including extension. Then they'll want to know what "can't drag" means. You get the drop cursor, but nothing happens when you release it? If so, where are you dropping it? Or does the drop cursor never appear?
I understand your frustration, but a little courtesy and respect goes a long way around here.
Steve
Robert Huttinger
please email "sup...@barebones.com" rather than posting to the group.
NotInUse
(at least as I interpret it) that this is my first rodeo. I assure
you, it's not.
I see the same (faulty) results on multiple Macs running different OS
versions. Not one system. This immediately rules out corrupt
preferences or other system specific items. I realize (and have
posted) that it does not rule out user error. I, honestly, do not see
how, after 10+ years of use, user error could be the issue. But who
know.. I guess stranger things have happened. Point being, I'm not new
to the app.. or Macs.. or any of this.... I am left to believe it's
fault in the app itself.
I can absolutely state, without fail that no image insertion, whether
via the HTML palette button, or dragging from the desktop to a
document or from anywhere is inserting the full HTML markup for an
image tag. I get <img src="file path" alt="<* some text *>" /> if I
use the HTML palette button and that's it. I get NOTHING if I drag and
drop.. and by nothing I mean NOTHING. No cursor change, no insertion
of anything, no indication that anything has been dragged to the
document window. Nothing at all.
I've shown the BareBones team my support for many, many years with my
money and recommendations. And in all that time, I've never asked for
any support or anything other than a functional app. Which is all I'm
asking for here. If you all don't seem to like how I ask for a
functional app... well.. you didn't need to respond, now did you?
It's a purchase, and I don't like purchasing products only to receive
defective items. I expect certain hiccups and issue with new release
software. But it's not standard to suddenly be missing core features.
If I purchased an upgrade to Photoshop and suddenly found I had no
brushes at all.. I'd be pressing Adobe as to why.
None of what I posted is a personal attack. It's business. And no
matter how much you folks want to make it seem as though I'm
personally attacking someone, I am not.
On Jul 22, 8:22 am, Robert Huttinger <roberthuttin...@gmail.com>
wrote:
Tim Gray
>As written, and tested during the beta cycle, dragging an image into an
>HTML document inserts complete and correct markup:
>
><img src="file://localhost/Users/kalkwarf/Pictures/Fabulous%20Dog.jpg"
>alt="Fabulous Dog.jpg" width="1280" height="960">
>
>If you are seeing different results, there is either a bug in the
>software, or a mis-aligned expectation.
I don't have a dog in this fight, but for what it's worth, when I drag
an image file into an open html document in BBEdit 10, nothing happens.
John Delacour
>I can absolutely state, without fail that no image insertion, whether
>via the HTML palette button, or dragging from the desktop to a
>document or from anywhere is inserting the full HTML markup for an
>image tag. I get <img src="file path" alt="<* some text *>" /> if I
>use the HTML palette button and that's it. I get NOTHING if I drag and
>drop.. and by nothing I mean NOTHING.
I can only presume the 'document' you are referring to is not an html
document because both things work fine here.
Type control-command-n, type return, drag an image from the Finder to
the insersion point. Are you saying that produces nothing?
JD
Tim Gray
>Type control-command-n, type return, drag an image from the Finder to
>the insersion point. Are you saying that produces nothing?
That's what happens for me. The jpg icon gains a green plus badge once
the cursor is in the BBEdit html document. The insertion point tracks
the mouse to the right line, but when I drop the file, nothing happens.
John Delacour
>On Jul 22, 2011 at 06:42 PM +0100, John Delacour wrote:
>>Type control-command-n, type return, drag an image from the Finder
>>to the insertion point. Are you saying that produces nothing?
>
>That's what happens for me. The jpg icon gains a green plus badge
>once the cursor is in the BBEdit html document. The insertion point
>tracks the mouse to the right line, but when I drop the file,
>nothing happens.
Well it works fine here in 10.6.7 so perhaps it's a Lion thing,
something I'll be in a position to tell in about 5 years' time.
JD
NotInUse
Les Weber
Just tried dragging an image from the desktop to an unsaved html document. Img tag was put in with alt, width and height.
Do you have the document language type set to html?
--Les
> --
> You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups.
> To post to this group, send email to bbe...@googlegroups.com
> To unsubscribe from this group, send email to
> bbedit+un...@googlegroups.com
> For more options, visit this group at
> <http://groups.google.com/group/bbedit?hl=en>
> If you have a feature request or would like to report a problem, please email "sup...@barebones.com" rather than posting to the group.
NotInUse
template I've used for years.
....and yes.. I'm saying that produces nothing.
Tim Gray
>Well it works fine here in 10.6.7 so perhaps it's a Lion thing,
>something I'll be in a position to tell in about 5 years' time.
Yes, I'm on Lion.
Seth Dillingham
>I appreciate the responses, but you all seem to have the impression
>(at least as I interpret it) that this is my first rodeo. I assure
>you, it's not.
No, I think we just don't care how experienced you are. It makes
no difference.
That's not a personal attack, it's just the blunt truth.
>I see the same (faulty) results on multiple Macs running different OS
>versions. Not one system. This immediately rules out corrupt
>preferences or other system specific items. I realize (and have
>posted) that it does not rule out user error. I, honestly, do not see
>how, after 10+ years of use, user error could be the issue. But who
>know.. I guess stranger things have happened. Point being, I'm not new
>to the app.. or Macs.. or any of this.... I am left to believe it's
>fault in the app itself.
Perhaps it is a fault in the app itself. So?
How is being exceptionally rude on a mailing list of other users
going to help?
This is why you're getting the responses you're so unhappy
about. The main point of most of your posts is NOT that the app
isn't acting working how you think it should, but rather that
you should be able to report that fact in whatever voice you
like, in any forum you choose, and still get professional support.
Yet this is the BBEdit users discussion list, not the Bare Bones
support forum. The only official channel for support is via the
mailing address to which you already wrote (apparently). So
bringing this attitude here suggests that you are either mad at
us, the users, for the app not working correctly, or you want to
waste our time with rants about the company who makes the
software we're all using.
So which is it?
>I can absolutely state, without fail that no image insertion, whether
>via the HTML palette button, or dragging from the desktop to a
>document or from anywhere is inserting the full HTML markup for an
>image tag.
That's not true, because it's working just fine for me.
But what you probably meant is to add, "on my machine, and I'd
like help understanding why that is while I wait for the very
busy folks at Bare Bones to get back to me on my support request."
Right?
>I get <img src="file path" alt="<* some text *>" />
There might actually be something of a clue there... when I
insert an image, I don't get the XML tag-closing thing at the
end. I hate to ask this (as it will probably just prompt another
story about the rodeos you've been to), but are you 100% certain
you're running version 10? :-D
>I've shown the BareBones team my support for many, many years with my
>money and recommendations.
Why are you telling us this? We don't care. We're all customers.
Around here, the rules of thumb are generally: Ask polite
questions, get excellent answers from some of the smartest
people around. Whine too much, and at best you're on your own.
>And in all that time, I've never asked for
>any support or anything other than a functional app. Which is all I'm
>asking for here. If you all don't seem to like how I ask for a
>functional app... well.. you didn't need to respond, now did you?
Again, I think you've missed the fact that this is the user
list, not the support forum.
>It's a purchase, and I don't like purchasing products only to receive
>defective items. I expect certain hiccups and issue with new release
>software. But it's not standard to suddenly be missing core features.
You can take our word for it that this "core feature" is working
for most of us. If it weren't working during the beta, I
personally would have reported it, but it is working quite
nicely OMM. (But then, developers always say that...)
None of what I've said here is a personal attack, though you're
free to take it that way if you choose to.
Seth
Seth Dillingham
>I can only presume the 'document' you are referring to is not an html document because both things work fine here.
I did notice that new documents are no longer created as HTML by
default OMM, and I seem to have misplaced the "default language" setting.
NotInUse
on their support pages.
As a user list.. okay I can better understand some of the reactions.
My apologies if users were offended. Not my intention at all.
And again.. I'm dealing with multiple machines and multiple OS
versions so this is not an isolated issue here. If it were one machine
with the issue I would naturally assume it's the machine. But it's not
one machine.. and it's not one OS either. And yes it's BBEdit 10.
There's little mistaking it when you see the HTML Palette.
As posted before, I have emailed BareBones and now have had a
response. Initial response was the same as here.. just drag and drop.
I had to make a movie showing nothing happening and they've now asked
for the html file. Although, this happens with any file. It's clearly
a bug in the app.
Ken Lanxner
be working for some and not for others and I am sure Barebones
will eventually be able to sort out the reason(s) why.
Meanwhile, I filed a bug report with as much information as I
thought was relevant.
For those who get nothing dragging an image file, what about
dragging another html file to get an anchor tag? That does work
for me (although it also opens the dragged file and changes
focus to it).
Always curious to see what seems to be a bug that isn't a bug
for some. Meanwhile, let's not assume that because it is working
for you, there must be something wrong with the rest of us. :-)
Ken
lpw...@mac.com (Les Weber) wrote on 7/22/11 10:35 AM
>Just tried dragging an image from the desktop to an unsaved html
>document. Img tag was put in with alt, width and height. Do you have
>the document language type set to html?
--
Simple Lives Web Design
http://simplelives.com
Matt Strange
I'm seeing in BBEdit 10, and I must say:
I really thought BBEdit users would, in general, be much less juvenile
that what I'm seeing here. "NonInUse" asks an even-tempered question,
even tosses in some self-depreciation, and you people jump all over
him? What's the deal?
Sure, he tossed one light barb in there, but come on people! Stop
attacking the person and answer the questions. As is obvious from some
of the reasonable posts, there IS a problem here and it is potentially
crippling to somebody who makes their living writing HTML. Jumping on
the messenger simply because he expressed a little frustration along
with his question is really out of line.
Now I'll get off my soapbox and go back to searching to see if
anybody's found the problem I've encountered.
Seth Dillingham
>And yes it's BBEdit 10.
>There's little mistaking it when you see the HTML Palette.
Agreed.
...
>I had to make a movie showing nothing happening and they've now asked
>for the html file. Although, this happens with any file. It's clearly
>a bug in the app.
I ran some tests here.
The behavior I'm seeing is exactly as you describe if I set the
language to "(none)".
I'm not suggesting that yours is set to "(none)", but rather
that something may be confusing BBEdit on your machines into
thinking your HTML documents are not really HTML documents.
You say it happens with any document? How widely have you tested
that? Have you tried creating a completely new, blank,
plain-text document and setting it's language to HTML, then
immediately dropping an image into that empty window?
I ask that because BBEdit is known to use some of the tags in an
HTML document to figure out what kind of document it is (that's
why you were getting the xhtml version of the img tag). So
perhaps your HTML has something in it that the app finds off-putting.
Just offering suggestions, but that's the last of them.
Hopefully they'll help you figure it out soon.
Seth
Tim Gray
>For those who get nothing dragging an image file, what about dragging
>another html file to get an anchor tag? That does work for me
>(although it also opens the dragged file and changes focus to it).
Yes, that worked for me too. Though dragged file was not opened. Just
the anchor tag was inserted.
NotInUse
Seems to be an issue with remnants of older versions on the system.
A .plist file created by a legacy issue is not written correctly for
v10. This causes the drag/drop to fail.
So how to fix it....
OS 10.6.x or earlier.....
Go to [volumes]/Users/[your account]/Library/Preferences.
find com.barebones.bbedit.plist
NOTE: There are many barebones preference files, only this particular
file is a problem. You can leave all other barebones files you find
alone. Move com.barebones.bbedit.plist to your desktop (or simply
trash it) then restart BBEdit 10. You may need to reenter your serial
number. You'll also have to reset any specific preferences you changed
previously. However, the drag/drop should then be functional.
To Fix in OS10.7.
In the Finder, choose Go > Go To Folder.. from the menu
Type "~/Library" (without the quotes) in the box presented.
That will open the users Library folder. Go to Library/Preferences
find com.barebones.bbedit.plist
NOTE: There are many barebones preference files, only this particular
file is a problem. You can leave all other barebones files you find
alone. Move com.barebones.bbedit.plist to your desktop (or simply
trash it) then restart BBEdit 10. You may need to reenter your serial
number. You'll also have to reset any specific preferences you changed
previously. However, the drag/drop should then be functional.
The issue seems to present itself when a previous version has already
been installed.
And I'll admit, my bbedit prefs file is probably at least 2 versions
old. So in the end.. it could be construed as user error... I'm an
idiot.. a fool.. a dolt.. and deserve a lashing.
I hope my posts help other users.
Geoff
1) Chose the menu option File->New->HTML Document...
2) Clicked OK
3) Typed the sentence "This is a document" with paragraph tags around
it (I don't know if they get smushed in the Google Groups HTML
interface, so I'm not including them here".
4) In the Finder, located a jpg file on my disk and dragged it to the
point of the text after the preceding sentence. This appeared (I have
deliberately omitted the angle brackets): img src="file://localhost/
Users/xxxxxxxxx/Documents/xxxxxxxx/sg-calltoaction-small.jpg" alt="sg-
calltoaction-small.jpg" width="400" height="267"
I'm running Lion and BBEdit 10.
John Delacour
>I did notice that new documents are no longer created as HTML by
>default OMM, and I seem to have misplaced the "default language"
>setting.
I don't know how wide this new blindness is, but the script I use for
creating a new Perl document:
using terms from application "BBEdit"
make window with properties {source language:"perl",
text:"#!/usr/local/bin/perl" & return & "use strict;" & return & "use
feature qw( say state switch);" & return}
end using terms from
now creates a plain languageless document when in BBE 9 the document
coloured the syntax. Having noted Rich's recent warning, I changed
'window' to 'document' but still the syntax is not coloured and the
doc type is 'none'.
On the other hand, if I create a new text document and paste in the
Perl shebang, the syntax is immediately coloured and the doc language
is automatically changed to 'Perl'.
To say the least there seems to be some inconsistency here that did
dot exist before.
On the positive side I am delighted to see (fingers crossed) that
Perl errors can now be dismissed without redundant and meaningless
save dialogs -- a feature I complained about several times when it
intruded itself into BBE 9.
JD
Steve Kalkwarf
> Seems to be an issue with remnants of older versions on the system.
> A .plist file created by a legacy issue is not written correctly for
> v10. This causes the drag/drop to fail.
Indeed. Thanks for the assistance narrowing it down.
We'll fix it in code before 10.0.1 is final, but as a workaround you can go to the terminal, and type these two commands:
defaults delete com.barebones.bbedit HTMLImageDropMarkup_UseFilenameForAlternativeText
defaults delete com.barebones.bbedit HTMLImageDropMarkup_InsertEmptyALTAttribute
to fix the drops.
There's a separate bug that _may_ prevent sizes from being added. If that affects you:
defaults delete com.barebones.bbedit HTMLImageDropMarkup_HasSize
Sorry for the hassle,
Steve
Tim Gray
>We'll fix it in code before 10.0.1 is final, but as a workaround you can go to the terminal, and type these two commands:
>
>defaults delete com.barebones.bbedit HTMLImageDropMarkup_UseFilenameForAlternativeText
>defaults delete com.barebones.bbedit HTMLImageDropMarkup_InsertEmptyALTAttribute
>
>to fix the drops.
Works great. Thanks.
Charlie Garrison
On 22/07/11 at 9:49 PM +0100, John Delacour
<johnde...@gmail.com> wrote:
>using terms from application "BBEdit"
>make window with properties {source language:"perl",
>text:"#!/usr/local/bin/perl" & return & "use strict;" & return
>& "use feature qw( say state switch);" & return}
>end using terms from
>
>now creates a plain languageless document when in BBE 9 the
>document coloured the syntax. Having noted Rich's recent
>warning, I changed 'window' to 'document' but still the syntax
>is not coloured and the doc type is 'none'.
Not sure it if it makes any difference, but try setting source
language to "Perl" instead.
If that doesn't fix it then manually set a document to "Perl"
and use AppleScript to get the Source Language; use the same
returned value in your script.
Charlie
--
Ꮚ Charlie Garrison ♊ <garr...@zeta.org.au>
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
〠 http://www.ietf.org/rfc/rfc1855.txt
LuKreme
On Jul 22, 2011, at 9:10, NotInUse <pst....@gmail.com> wrote:
> solution for no auto-insertion of image
> dimensions
I've tested this a couple of times and I don't see the behavior you describe. When I drag an image into an HTML doc I get a fully formed IMF tag with an empty alt=""
Watts Martin
> I've tested this a couple of times and I don't see the behavior you
> describe. When I drag an image into an HTML doc I get a fully formed
> IMG tag with an empty alt=""
Same here, and a bit of quick testing shows that it's even respecting
the DOCTYPE tag at the top of the file. I can only get the "nothing is
produced" error that "NotInUse" is reporting by changing the language to
something other than HTML in the status bar.
While this is probably an annoying suggestion, I wonder if it's
something incompatible in the preference file or application support
folder. I have, on both upgrading to BBEdit 10 from 9.6 and to 9.6
from... 6.5? 7.something? (just say it was a while), gotten some highly
curious behavior with old preference files.
--
Watts Martin <lay...@gmail.com>
JB
key - Library appears in the list. Click and go.
Maarten Sneep
On 23 jul. 2011, at 16:15, JB wrote:
> It's easier than that... in the Go menu, just hold down the option
> key - Library appears in the list. Click and go.
And if you would like to permanently revert Apple's decision, and have the developers tools installed:
SetFile -a v Library/
from the terminal makes the Library permanently visible.
Best,
Maarten
LuKreme
Ok I broke it. If I drag Screen Shot 2011-07-23 at 11.30.15 AM into either an editing BBEdit HTML doc or a. Brand new one, nothing happens
10.7 & 10.0.0
John Delacour
>Ok I broke it. If I drag Screen Shot 2011-07-23 at 11.30.15 AM into
>either an editing BBEdit HTML doc or a. Brand new one, nothing
>happens
>
>10.7 & 10.0.0
No problem here in 10.6.8
I created the file like this:
Steve Piercy
> Ok I broke it. If I drag Screen Shot 2011-07-23 at 11.30.15 AM into either an editing BBEdit HTML doc or a. Brand new one, nothing happens
>
> 10.7 & 10.0.0
solution that Barebones provided earlier in this thread.
http://groups.google.com/group/bbedit/msg/cd9fdbe6cb8d51ea
I had a problem myself last year when upgrading from 9.5.1 to 9.6. I
think only I and a couple of other people had the issue, and the
majority of users reported they could not reproduce the issue, just
like folks are doing in this thread.
I cannot remember what the cause was, but working directly with
sup...@barebones.com resolved the issue by using one of the betas. If
this issue affects you, then I suggest you contact BBEdit Support.
--steve
François Schiettecatte
Sweet, I was just wondering how to do that, thanks!
François
Marc
On 22 jul, 17:21, Steve Kalkwarf <kalkw...@barebones.com> wrote:
>
> As written, and tested during the beta cycle, dragging an image into an HTML document inserts complete and correct markup:
>
> <img src="file://localhost/Users/kalkwarf/Pictures/Fabulous%20Dog.jpg" alt="Fabulous Dog.jpg" width="1280" height="960">
>
> If you are seeing different results, there is either a bug in the software, or a mis-aligned expectation.
>
I'm having the same problems with img insertion as NotinUse is
reporting.
I can drag an image into the html file, but nothing happens at all. No
dialog pops up.
The only way to get an image into the file is by using the menu
choice.
The dialog that pops up, doesn't have anything filled out
automatically and when I select a local file it gets inserted with the
full path to the file on my server.
I just want relative filepaths!!
I just reverted to BBEdit 9.3 as 10 is just twice as much work.
Waiting for the fix.
Marc.
Eros9
BBEdit since near the beginning and always found every upgrade to be
an improvement. Now I've spent $40 to revert to 9.6. I trust that v10
will be worth switching to at some point ...
My main issue is with anchor tags. In v9, I can highlight a URL, hit
cmd-ctl-A, and hit Enter. Voila!
Now in v10, I highlight the URL, hit cmd-c, hit cmd-ctl-a, type in hr
(autocompletes to href), tab, tab again, hit cmd-v, and hit Enter.
Whew!
bobembry
Roland Küffner
Am 28.08.2011 um 16:33 schrieb Eros9:
> My main issue is with anchor tags. In v9, I can highlight a URL, hit
> cmd-ctl-A, and hit Enter. Voila!
>
> Now in v10, I highlight the URL, hit cmd-c, hit cmd-ctl-a, type in hr
> (autocompletes to href), tab, tab again, hit cmd-v, and hit Enter.
> Whew!
The short version (cmd+ctl+a followed by return) works fine for me in v10. So, for me this behavior is exactly the same as it was in v9. Maybe you are facing some issues with your preferences. Maybe this was broken and has been repaired in one of the last updates (I'm using v3079 as announced on this list a few days ago and I don't remember if I used that shortcut before that update).
Maybe you should contact support to get assistance on the topic.
Regards,
Roland
Eros9
step before and 5 after to turn existing URL text into a link, where
in v9 it required 1.
On Aug 29, 5:59 am, Roland Küffner <medienmeis...@googlemail.com>
wrote:
Eros9
with the highlighted URL.
Hooray!