Re: BBEdit TXT Files won't open in iCloud Drive for iOS

[Mike Warren]

On Saturday, July 15, 2017 at 10:44:33 PM UTC-4, Jimmbo wrote:
>
> Viewing iCloud Drive (via Apple's dedicated app) on iPad and iPhone, all 
> my BBEdit TXT files display icons from FTP Client Pro. 
>
> The files do open in the iCloud Drive app, with "Kind" as "data". Text 
> looks awful (and is un-editable). 
>

My text files open as expected and are editable. Kind = Text. 

Do you use the .txt file extension?

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

BBEdit TXT Files won't open in iCloud Drive for iOS

[Jimmbo]

Viewing iCloud Drive (via Apple's dedicated app) on iPad and iPhone, all my 
BBEdit TXT files display icons from FTP Client Pro. 

The files do open in the iCloud Drive app, with "Kind" as "data". Text 
looks awful (and is un-editable). 

If I choose to import to Notes, it imports as a useless data file. It 
doesn't grab the text. Ugh.

There's no way to config the share menu to enable "Open in Editorial" (my 
iOS text editor).

Any suggestions? iOS really should be a lot more graceful about opening TXT 
files! This feels troublingly like data rot - not something I ever expected 
re: TXT files!


JIMMBO

-- 
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: Files won't open

[Doug McNutt]

At 19:02 -0700 10/22/11, Watts Martin wrote:
>On Oct 21, 2011, at 16:43 , Doug McNutt wrote:
>
>>bbedit will not process files that have mixed line ends.
>>It won't even allow you to repair such files.
>>As an example try opening a bbedit worksheet as a plain text file.
>>
>
>I put a few commands in a new blank worksheet, saved it as "testme.worksheet," 
>then forced it to open as a new plain text file by opening it on the command 
>line with:
>
>   cat testme.worksheet | bbedit
>
>...and it opened as a text file just fine. What is it you were trying?


Well.  I might have been a bit brusque.  Today, using bbedit  8.5.2 which is as 
far as I can go with X 10.3.9 which is as far as I can go and still use my 
SE/30 file server. . .

I can in fact open files, such as a bbedit worksheet, in text mode.  I swear 
there was a time when bbedit would simply refuse to open such files.  Linux 
gedit continues to do just that and I do remember comparing it to bbedit at the 
time. It was when Bare Bones started using 16 bit words during its editing 
process that I first had problems. That might have been version 8.0. Version 
8.5 still works fine on this 8500 but there an escaped n means 0D and the 
escape character is OPTION d. Yes. I still use MPW.

Version 8.5.2 bbedit worksheets are really XML files of the Apple plist 
variety. The line ends for the XML part are 0A or \n . The worksheet part is a 
dict. entry inside of the XML which uses 0D or \r to separate lines as they 
would be interpreted in a Terminal worksheet.

If you open a worksheet as text, piping as above is one way, the file appears 
to be plain text and, except for visibility of the XML parts, is just like the 
worksheet. But you'll have trouble editing it and saving the results as a 
working worksheet. I really wanted to do things like that so I could muck with 
the saved startup directory and perhaps more like automatically running a shell 
script as each worksheet is opened.

When you save a worksheet opened that way all line ends will be converted to 
the end character specified in the tool bar at the bottom of the edit window. 
That means the modified file cannot have different ends for the XML and dict. 
parts as apparently required by the format. After modification and storage it 
will not work as a worksheet regardless of the creator and type settings. I 
always keep file specific settings in its resource fork.  Bbedit also can save 
such things in a time-expiring list in someone's home directory. The difference 
might be important in the piping technique used above.

Actually, worksheets remain a small part of the real problem.  I work with 
machine tools and other text-like command or assembler files that need viewing 
of variable width tab separated columns, and a couple of different line end 
characters that are used for different purposes.  Bare Bones does not feel it 
appropriate to support those things and neither does anyone else.  Spreadsheets 
are what I use when I can but more often it's home grown perl scripts without 
the benefits of a GUI editor. Full fledged word processors offer entirely too 
much and often make it nearly impossible to save without any markups at all. 
Nisus in its earlier versions was nice for that but as of OS neXt it's just 
like all of the others.

  might be interesting to some. 
It's  Applescripted C that I worked out to work with line ends. Source code 
included. There was another gentleman on this list whose problems were similar 
to mine a few years ago. He offered some C code that worked with 0A and 0D. I 
dressed it up to include 0D0A pairs and provided a drag and drop AppleScript 
interface which changes line ends and allows for an "Examine" that generates a 
count of all 3 line ends.

  Also has some stuff that allows 
worksheets to execute some csh code as they are opened. It does not try to edit 
the internals of a worksheet.


-- 

--> From the U S of A, the only socialist country that refuses to admit it. <--

-- 
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 bbedit@googlegroups.com
To unsubscribe from this group, send email to
bbedit+unsubscr...@googlegroups.com
For more options, visit this group at

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: 

Re: Files won't open

[Watts Martin]

On Oct 21, 2011, at 16:43 , Doug McNutt wrote:

> bbedit will not process files that have mixed line ends.
> 
> It won't even allow you to repair such files.
> 
> As an example try opening a bbedit worksheet as a plain text file.


I put a few commands in a new blank worksheet, saved it as "testme.worksheet," 
then forced it to open as a new plain text file by opening it on the command 
line with:

cat testme.worksheet | bbedit

...and it opened as a text file just fine. What is it you were trying?

-- 
Watts Martin 



smime.p7s
Description: S/MIME cryptographic signature

Re: Files won't open

[Greg Reyna]

Ok, I'm an idiot.   The BBEdit window was so far south on my screen it
must have disappeared behind the dock.  After a reboot  I glanced down
to the right of my multi-tiny-icon dock and saw BBEdit's little right-
side-of-the-title-bar button peeking out and making faces at me.

My text files are all plain vanilla ascii so it didn't make sense that
they wouldn't open!

On Oct 21, 6:13 pm, David Kelly  wrote:
> On Oct 21, 2011, at 6:43 PM, Doug McNutt wrote:
>
> > bbedit will not process files that have mixed line ends.
>
> > It won't even allow you to repair such files.
>
> No way! BBEdit is my FIRST CHOICE for repairing such files. Do it all the 
> time.
>
> --
> David Kelly N4HHE, dke...@hiwaay.net
> 
> Whom computers would destroy, they must first drive mad.

-- 
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 bbedit@googlegroups.com
To unsubscribe from this group, send email to
bbedit+unsubscr...@googlegroups.com
For more options, visit this group at

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: 

Re: Files won't open

[David Kelly]

On Oct 21, 2011, at 6:43 PM, Doug McNutt wrote:

> bbedit will not process files that have mixed line ends.
> 
> It won't even allow you to repair such files.

No way! BBEdit is my FIRST CHOICE for repairing such files. Do it all the time.

--
David Kelly N4HHE, dke...@hiwaay.net

Whom computers would destroy, they must first drive mad.



-- 
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 bbedit@googlegroups.com
To unsubscribe from this group, send email to
bbedit+unsubscr...@googlegroups.com
For more options, visit this group at

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: 

Re: Files won't open

[Doug McNutt]

At 14:34 -0700 10/21/11, Greg Reyna wrote:
>I've used BBEdit for years so I'm very surprised that suddenly it
>won't open some text files.  Nothing happens.  I just updated to 10.1
>from 10.0.1, but that didn't help.  I'd delete the prefs file but I'm
>not sure where it is...is that what I should do?  This is odd.
>Recently, as a warning that something was amiss, despite setting
>BBEdit's prefs to re-open the files that had been open on last quit,
>it stopped doing that and didn't open anything on startup.


bbedit will not process files that have mixed line ends.

It won't even allow you to repair such files.

As an example try opening a bbedit worksheet as a plain text file.
-- 

--> From the U S of A, the only socialist country that refuses to admit it. <--

-- 
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 bbedit@googlegroups.com
To unsubscribe from this group, send email to
bbedit+unsubscr...@googlegroups.com
For more options, visit this group at

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: 

Files won't open

[Greg Reyna]

I've used BBEdit for years so I'm very surprised that suddenly it
won't open some text files.  Nothing happens.  I just updated to 10.1
from 10.0.1, but that didn't help.  I'd delete the prefs file but I'm
not sure where it is...is that what I should do?  This is odd.
Recently, as a warning that something was amiss, despite setting
BBEdit's prefs to re-open the files that had been open on last quit,
it stopped doing that and didn't open anything on startup.

Thanks for any advice,
Greg
---

8-core Mac Pro (2010); OS 10.6.8, BBEdit 10.1

-- 
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 bbedit@googlegroups.com
To unsubscribe from this group, send email to
bbedit+unsubscr...@googlegroups.com
For more options, visit this group at

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: