Re: Searching Typescript (.ts) files in v12.0?

[Joe Lapp]

Your support for dark workspaces and Typescript searches came just in time.

I was getting used to a dark theme in Visual Studio Code, but I've thrown 
up my hands in frustration at VSC's nonsensical autoindentation. I was 
keeping files open in both BBedit and VSC anyway. Glad I can now return to 
using BBedit all the way.

However, I have a feature request. In VSC, I can specify color theme deltas 
relative to the current color theme. That way my deltas stick even as the 
original color theme gets maintained. I get theme updates while still 
getting my preferences. Win-win. I'd like the same in BBedit.

I'll send a note to support.

~joe

-- 
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: Command-Backspace for spaces between word?

[Kerri Hicks]

Can you explain in a bit more detail the issue that's annoying you?

--Kerri

On Wed, Oct 25, 2017 at 3:26 PM, KerbyLane  wrote:

> Ug.  Why is this still an issue?  So annoying.  I can't find any other app
> that works like this.
>
> https://groups.google.com/forum/#!forum/bbedit
>
> --
> 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.
>

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

Entering path for Save As filename doesn't go to the path :-(

[Everywhere is Nowhere]

BBEdit is the first editor I've used where if I enter in "Save As" a file 
path, it doesn't change the default location to the path to the specified 
path and then save the file whose name is the final component of the path 
there.

That's pretty frustrating, because it means I have to tedious navigate to 
known long paths using the pulldown selector, and should not have to.

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

[ANN] BBEdit 12.0.2 (400013) pre-release

[Rich Siegel]

Good { morning, afternoon, evening },

We're working on an update to BBEdit 12.0 to address a few 
recently reported issues.


Note that this is a _pre-release_ version. The intent is to fix 
bugs and address areas of improvement based on what our 
customers have reported. However, since the software is at this 
point not fully tested, there _may_ be bugs and regressions.


If this prospect makes you nervous, then sticking with the 
public release versions is your best course of action. Nobody 
will be offended if you choose to do so; you're under no 
obligation to install and use anything but a public release. :-)


Following is a summary of changes since the most recent 
pre-release build. Complete change notes for all of the 
pre-release builds in this cycle are available here: .


The change notes are organized into additions, changes, and 
fixes, and are annotated where appropriate with case numbers. So 
if you recognize a number corresponding to a support case that 
was opened for you, you can now verify that it's been fixed 
correctly. Please take the time to review the changes before 
using the new build -- it'll be worth your time.


One final note: If you run into a bug in a pre-release version, 
PLEASE DO NOT REPORT THE BUG TO THE LIST. This includes asking 
about whether others have seen the same problem. Instead, please 
send a bug report to  and we will deal 
with it there. This will help us keep the list discussion on 
topic and productive for all list members.




version 12.0.2 (400013) (2017-10-25)

Additions
-

o   (none in this build)

Changes
---

o   (none in this build)

Fixes
-

*   [346555, 346932] Fixed bug in which menu items indicated by
searching for them using the Help search box would be 
disabled in

situations where they shouldn't have been.

*   [347048, 347062] Fixed bug in which the "Update" scripting event
would return an error.

*   [347058] BBEdit now writes out temporary files for live preview
windows with `644` permissions, so that other processes 
(such as

Apache) can read the file if necessary.

*   [347076] Fixed a bug in which a request from the command line
(or elsewhere) to open an sftp URL without a username (or
password) would return a -50 error.

*   [346662, 347057] BBEdit will (once again) warn about malformed
UTF-8 files rather than simply refusing to open them.

*   [347080, 347128, 347147, 347150] Fixed a collection of bugs that
conspired to slow down SFTP operations, particularly the initial
connection to the remote server.

*   [347161, 347166] Fixed bug in which the "Allow the Escape 
key to
trigger text completion" preference was ignored, and the 
`Esc` key

did not work to trigger completions.

*   [347191] Rewrote ancestor discovery code (used for finding
`.git`, `.svn`, and such like) to improve performance as 
well as

behavior when used for files that aren't on the boot volume.

*   [347125] Fixed crash which could occur when certain changes were
made in the Font panel while adjusting a font preference.

*   [346674] Fixed bug in which the "New Text Window" and "All
Running Browsers" commands were left off the "Preview In" submenu
on the Markup menu.

*   Fixed bug in which the window resulting from a Preview/New Text
Window operation didn't have the desired title.

*   Fixed bug in which certain errors reported during attempts to
automatically back a file up were not reported correctly.

*   [347177] Fixed bug in which contextual-menu commands in the
Currently Open Documents list of a project sidebar would be
targeted to the Project list instead.

*   [346509] Made a change to the "Rearrange Columns" panel so that
it can be expanded horizontally to accommodate long column header
names.

*   Fixed a bug in which preview temp files generated for live
previews didn't have the appropriate extended attributes which
allowed them to be excluded from various site operations.

*   [346590] Fixed bug in which *no* completion sources were allowed
for plain-text languages (Text File, CSV, TSV), which was not
necessarily a useful outcome.

*   [347295] Fixed crash when trying to remove customized settings
for a specific language (in the Languages settings).

*   Fixed layout bugs in the completion panel with certain font/size
combinations.

*   Made `ctl-n` and `ctl-p` functional again in the completion
panel.

*   Fixed crash which would occur when quitting the application
while the completion panel was open.

*   Fixed bug in which window activation changes were mismanaged by
the application. Although there weren't any reported bugs
attributable to this, it was wrong and needed to be fixed.

*   [345356] Fixed bug in which zooming (option-click on the 

Re: Can't assign certain key combinations to clippings

[Brian Gollands]

Thanks for testing that, Kendall. I guess that's the next step -- deleting 
prefs and maybe temporarily uninstalling certain apps like KM and KC. The 
problem isn't a showstopper, but there are only so many key combinations 
that I can remember and those are nice simple ones!

On Tuesday, October 24, 2017 at 10:54:01 PM UTC-4, Kendall Conrad wrote:
>
> With OS 10.11.6 and BBEdit 12.0.1 I was able to successfully assign 
> Ctrl+Opt+Cmd+P (and C, T. S was already assigned) to a clipping and use it.
>
> You may want to try and backup your settings/preferences somewhere and 
> delete them to see if there's something funny with it as a way to narrow 
> down the problem. I don't have Keyboard Maestro or KeyCue installed so 
> can't say if they are a factor.
>
> ~Kendall
>
> On Monday, October 23, 2017 at 2:12:25 PM UTC-4, Brian Gollands wrote:
>>
>> Using latest BBEdit and X.12 and I have had a number of clippings that I 
>> use for adding HTML to text. I had assigned shortcuts to a lot of these and 
>> in the last year sometime, some of them stopped working and I can't reset 
>> them. Only certain combinations won't allow me to set them in the Clippings 
>> palette (i.e., there is no response when I try to edit shortcuts and type 
>> something into the field). I am running Keyboard Maestro, but have turned 
>> it off, as well as checked for conflicting shortcut assignments. I also 
>> went into Sys Prefs and removed any conflicting shortcuts in Keyboards > 
>> Shortcuts. And KeyCue doesn't show any being used by the system. I also 
>> logged in as a new user to avoid any accumulated "baggage" -- no joy.
>>
>> Some of the problem shortcuts are:
>> ctl-opt-cmd-p
>> ctl-opt-cmd-s
>> ctl-opt-cmd-t
>> ctl-opt-cmd-c
>>
>> These don't seem to be used BBEdit. Can anyone think of any other place 
>> these might be assigned? Maybe an installed app uses those, but registers 
>> them system-wide, even though it's not open? Again, nothing shows in 
>> KeyCue. Any suggestions are most welcome. Thanks!
>>
>>

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