BBEdit instead of vi

Originally posted by AdmiralAK
Is pico even bundled anymore with unix distros ???
Click to expand...

Sure does.. remember, it's part of Pine.. _THE_ best email proggy for the command line.

vi is for those who are truely into sadism and self abuse.. and emacs is just plain overkill for anything other than code developement. I bought the O'Reilly books for both 7-8 years ago.. a text editor should NOT require a 300 page manual! (yeah, I know.. emacs is more than _just_ a text editor.. but alot of people aren't going to require the extra "functionality" of emacs to write a quick shell or pearl script.. for those people, pico works just fine)
 
I learned emacs for my CS programming.
The dept wanted us to learn vi too but it wasnt enforced so nothing sank in :p ... vi is so.... painful to learn & look at :p ....

I;ve never used pico... but I have used pine :D
 
I logged in as Root, but even after creating the alias, I still can't get BBEdit to open any files with Root privilages. I don't know how TommyWillB got it to work.

Any help would be appreciated...
 
The PC thing to say is that is all down to personal preferences.

But personally, I've yet to meet someone who can edit source code as fast as I can in Vi. Maybe I'm just not hanging with the right ppl? ;-)))

... and I was wondering how long it would take for the "editor wars" to break out here ;-)

BTW: I really can understand ppl NOT wanting to learn all the commands for Vi (hell, I don't know *all* of them yet, just when you think you've got it all down pat, you discover another feature hidden away somewhere ;-)) ... but like I say - I've yet to see anyone edit a file faster than I can in Vi!

Just my $0.02


C
 
... I just realised that the first line of my last post sounds like a *REALLY* bad pun! I assure one and all that it was certainly not meant as such ;-)
 
Originally posted by testuser
Tommy got this to work under 10.0. After the 10.1 Security Update you can no longer use sudo to run GUI apps as root.

If you download the latest version of BBEdit, it allows you to edit files owned by root (use "Open hidden" from the menu). It will give a dialog box that allows an authorized user to authenticate.
Click to expand...
Okay, I stand corrected... This has changed since 10.1...

But I just tried BBedit 6.5.2 and it give me an error when tryin to open a file owned by root, not an authenticate dialog. Am I doing something wrong?
 
Originally posted by LordCoven
But personally, I've yet to meet someone who can edit source code as fast as I can in Vi.
Click to expand...
Ahhhh! this is THE important detail.

If my sister and I begin the same task, me using BBEdit and her using vi, we both finish at the same time. If we switch, we still finish at the same time, but that time is 5 times slower than us doing the task on our preferred tool.

At the end of the day you should use the tool you are most comfortable with and fastest on.

(Although I might conceed that my sister & vi had the advantage knowing that vi will be installed on 99% of the machines she encounters [all *Nix boxes] while I have no such guarantee that BBEdit will be there. :( )
 
I just gave joe a try, but I'm not altogether satisfied with the result.

using jpico - inconsistent cutting and pasting behaviour:
"jpico filename": semi pico-like, cut cuts only the block you have selected. If you have no block selected, it cuts the line.
"jpico": pure joe-like, cuts the current line, no matter what you have selected.

using jmacs - (why would anyone want to imitate emacs interface?) - still can't get emacs sensible wrapping behaviour. I don't care for emacs, but it's the only unix editor I have found with soft-wrapping of text. So I start half an OS everytime I want to answer an e-mail in pine...

using joe - well, maybe I could get used to it, but is it really worth it? I dunno. Still no soft-wrapping.
 
BareBones now includes a bbedit shell command in BBEdit 6.5 , so forget my first post on this subject. :cool:
 
I did as exactly as you said. But when I open files that were created by root, they open as locked files and I can't edit them. They open this way whether I do sudo bb filename or if I su into root and then do bb filename. I don't get it. I would like to use this to edit files like /etc/httpd.conf but it will not let me unlock it. Any ideas on how to get around this?

Thanks,:)
SA
 
mine is 'bbedit.' And I use the free lite version.
I also use Tex-Edit Plus which i got ages ago because it's very applescriptable. My command for that is teplus.

A handy trick with apple event aware apps: you can set /usr/bin/osascript and run a script to set up your target app.
 
come on I thought this was a UNIX forum.

People dreaming that there is any finer text editor in the world than vim (vi improved). They obviously shouldn't be on a UNIX forum unless they are asking for advice. If you don't want to learn vi then you can't be serious about learning UNIX so get out of the terminal.

There is a reason that vi exists on ALL UNIX's its because it is still the best general purpose text editor there is. GUI's are not for editing text fast. GUI's specialise is WYSIWYG making things pretty. Not for moving text the fastest possible way.

If you need to make a formatted document use word/apple works. Need to process text, write code,edit files vim/vi is your man.

I do agree that vim/vi are one of the hardest editors to learn. But once you have learn't it you will never use another editor (for text) again.

btw once you have a terminal open BBedit (Bloody Bloated edit) count how long it takes.... the vi the file.....oooops it starts to fast to count.
 
Originally posted by mrjohns

...

They obviously shouldn't be on a UNIX forum unless they are asking for advice. If you don't want to learn vi then you can't be serious about learning UNIX so get out of the terminal.

...

GUI's are not for editing text fast. GUI's specialise is WYSIWYG making things pretty. Not for moving text the fastest possible way.
...
Click to expand...

Moving text is precisely what editors like BBEdit and Tex-Edit Plus do infinitely faster than vi. In fact the only slow editor i have right now is AbiWord. It shows a telling ignorance of clippings and drag and drop that "moving text" (vs. long regex subs or duplicated macros) would be the misexample chosen.

There is also a reason why every UNIX I know of lets you use a mouse.

I am very familiar with vi, nor is it hard to use, compared to ed. I do most of my quick-and-dirty editing in vi, and use sed for multiple files, unless i have to use awk or perl.

I like the regex capacity of BBEDit, and i have duplicated it with my script "Replace Regex" in Tex-Edit Plus. I use TE for formatted text, but a lot of that is html formatting derived from sophisticated regex/style combinations.

vi is clearly not superior to emacs or xemacs w/r/t plug-ins and modes. In that area it's also clearly inferior to BBEdit.

Moreover, recording in a UNIX command-line editor is a nightmare and with a Mac classic or X application it's a breeze.

Anyone who hates any technology developed after 1970 really won't enjoy OS X.

By the way i am releasing next month both an improved Classic/Dialog Director/Regex Commands version of Replace Regex and an AppleScript Studio version.

Both will handle styled text post-regex sub according to the rules of Tex-Edit Plus. They are slower than the old Replace Regex, but I found myself using BBEdit Lite for unstyled text anyway.
 
123123the127812687rain213123
1in3231231spain123123123fails123123
12324124mainly123123123on23124124the12312312plain123
12312on123123the123123
123123plain12312144

in vi the following command.

:%s/[0-9]*\([a-z]*\)[0-9]*/\1/g

produces

the rain
in spain fails
mainly on the plain
on the
plain

All without my hands leaving the keyboard!!


to insert a file's/clipping's contents into a file
move to the position you want it then type

:r filename.

copy 5 lines type

5Y

paste them type

p

move the first three characters of each of these 5 lines to the end of the line and make them upper case. (in vim only)

werTHE
freYUJ
wWeJKL
iyuKSM
IOsNMK

move your cursor to the 'w' of the first line then type
(Control V)4j2lx$p(control V)4j2lU


All without leaving the keyboard. Now this isn't for everyone and its probably slower if you don't know this stuff. But when you become a v i jedi then this is the fastest way to work. :)
 
Bah, I just use pico, it has the little bar on the bottom which says what everything does :)
Haven't taken the time to learn vi or emacs, pico works, right?
 
One advantage of knowing vi is that virtually every Unix based system out there has vi on it, while the same can't be said for pico or emacs...

So if you are in a position where you need to access some other machine and the only tool you have is emacs and it isn't installed...you're stuck.

I say this as one who by profession does Unix system administration on machines ranging from Solaris, AIX, Linux, Unixware, BSD...
 
You must log in or register to reply here.
Back
Top