Live data from Hacker News

BBEdit: Where Respect Is Due

apps.apple.com

41–50 of 177 posts

Re: BBEdit: Where Respect Is Due

#41
post #25

Earlier quoted context omitted.

> Since then, I've purchased BBEdit licenses, but use other editors when I need to hard wrap text to window width. BBEdit is incredibly scriptable and extensible. You could have written a short script in AppleScript, Perl, Ruby, Python, etc. to perform this task without leaving BBEdit.

[flagged]

BTW, BBEdit has a `hard wrap` scripting command with a limit option (page guide, window width, character width).

And, no, GPT is not a tool for factual verification, it creates probable chains of words that are likely to be found impressive by humans.

Re: BBEdit: Where Respect Is Due

#44
post #25

Earlier quoted context omitted.

> Since then, I've purchased BBEdit licenses, but use other editors when I need to hard wrap text to window width. BBEdit is incredibly scriptable and extensible. You could have written a short script in AppleScript, Perl, Ruby, Python, etc. to perform this task without leaving BBEdit.

[flagged]

Apologies all. Thank you for the information.

Re: BBEdit: Where Respect Is Due

#45
post #25

Earlier quoted context omitted.

> Since then, I've purchased BBEdit licenses, but use other editors when I need to hard wrap text to window width. BBEdit is incredibly scriptable and extensible. You could have written a short script in AppleScript, Perl, Ruby, Python, etc. to perform this task without leaving BBEdit.

[flagged]

> only use BBEdit once or twice a month (usually for multi-file search and replace via regex).

BBEdit’s regular expression support is jaw-dropping. Combined with how quickly it can update north of 10,000 files has kept me using BBedit for over 25 (!) years.

And I'm looking forward the next quarter century.

Re: BBEdit: Where Respect Is Due

#48
I never used it, but I certainly had to support web devs who did, and who needed me to open up FTP to the website so they could integrated-upload their markup.

There were a bunch of "does it do PASV" conversations. Because, FTP is sufficiently old-school (like telnet) that it believed in archaisms of how to open a distinct data port to a command port, and it made firewalls very unhappy unless you could use "passive mode" which was firewall friendly.

We wrote our own CMS using DAV (in Apache), and I wrote a push-publish engine which was on the "inside" master and would push out via rsync a checked out state respecting symlinks. It was kind-of like "stow" but for the networked web from a repo.

the BBEdit users weren't happy, they had their own idea of a CVS tree using "tortoiseCVS", we had many fine arguments about how to do it (most of the web was theirs but a small portion was not, and was in fact Apache::Perl rendered which was in a code repo, and combining multiple sources of authority over web state is always a very confusing place to be)

Re: BBEdit: Where Respect Is Due

#49

Wait, the impression I'm getting here is BBEdit is just Rich Siegel now? Does Barebones not have any other engineers working on BBEdit? Somewhat surprising, but props to Rich, that is some impressive work, above what I already thought was impressive work!

John Gruber of daringfireball fame and co-creator of Markdown worked there for awhile. His chapter on regex in the BBEdit manual is widely regarded as the best out there.
Post reply on HN