ping Slack dev team
in [Slackware]
|
Prev: LewPitcher.ca tops Google Search!
Next: Xorg and Intel Integrated Graphics Chipset: low resolution
From: Mike Jones on 27 Nov 2009 06:45 Responding to Aaron W. Hsu: > Mike Jones <Not(a)Arizona.Bay> writes: > >>Something as small as Nano = no, but Vi, which is huge (and complex) by >>comparison, is the standard? From the installation disk boot? This >>doesn't add up. > > If you want a small editor, and a minimalist installer that is quick and > easy to use, then why not look at the OpenBSD installer, which recently > had several improvements made for it, and which doesn't even include Vi, > but rather, uses ed, which is about as lightweight as you can get. > > Aaron W. Hsu The key here is not so much how big the editor is, but how usable it is to somebody who just needs an editor that works which doesn't need an extended course in incantational keysets just to edit a ****ing text file or two. Vi is like a full commercial flight simulator with realistic accident generation capacity built in, and ed is a legacy example of just why so many people developed editors that were nothing like ed. Thanks for the tip, but its not that useful under the circumstances. As a result of the input on this thread, its my conclusion that the Slackware install DVD isn't a viable recovery resource. I'll use RescueCD instead. Cheers. -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Helmut Hullen on 27 Nov 2009 06:46 Hallo, Grant, Du meintest am 27.11.09: > Hey I just tried that and it came up in elvis! (And one exits > vi's help the same as quitting a document, with :q, seems quite > natural to me :) Which of my 2 versions have you tried? What tells echo $VISUAL echo $EDITOR > ~$ which mcedit > /usr/bin/mcedit > This leaves me a bit doubtful now about the other vi alternatives you > gave? On my machines both alternatives work fine. >> Maybe you have to define >> >> Defaults editor=/usr/bin/mcedit /usr/bin/nano /bin/ed >> Defaults env_editor >> >> in your "/etc/sudoers". > Erk! And all that easier than remembering 'i', <esc> and :wq for vi? Sure! I define one time the entries for "/etc/sudoers", I define one time the entries for "/etc/profile.d/editor.sh", and after that (small) work I never need to remember the vi syntax. Ok - I need "wq" for exiting the "ed" editor. But that's nearly the same syntax as in (p.e.) "fdisk". Viele Gruesse Helmut "Ubuntu" - an African word, meaning "Slackware is too hard for me".
From: Eef Hartman on 27 Nov 2009 08:38 Keith Keller <kkeller-usenet(a)wombat.san-francisco.ca.us> wrote: > Since I haven't received any complaints about dovecot > in over five years, I have to assume that they never hit the bugs > mfor my purposes. entioned on that page. I don't know about the current versions but dovecot 0.99.14 was - as a imap4 server - a total piece of sh*t, it kept on currupting its own index files, thus either NOT sending new mail, or doubly sending old ones. This was on a mail server (Fedora), set up by the predessor of my colleague, which we are gradually retiring, so there is no use in updating that system. From the log OF that system: imap(admin): Nov 26 15:44:29 Error: IndexID mismatch for modify log file /home/admin/Mail//.imap/Trash/.imap.index.log imap(admin): Nov 26 15:45:03 Error: Corrupted binary tree file /home/admin/Mail//.imap/INBOX/.imap.index.tree: UID to be inserted isn't hi gher than existing (133 <= 134) imap(admin): Nov 26 15:45:03 Error: Corrupted binary tree file /home/admin/Mail//.imap/INBOX/.imap.index.tree: UID to be inserted isn't hi gher than existing (134 <= 134) imap(admin): Nov 27 07:55:08 Error: Corrupted binary tree file /home/admin/Mail//.imap/INBOX/.imap.index.tree: UID to be inserted isn't hi gher than existing (139 <= 152) imap(admin): Nov 27 07:55:08 Error: Corrupted binary tree file /home/admin/Mail//.imap/INBOX/.imap.index.tree: Tried to update nonexisting UID 132 imap(chunyang): Nov 27 09:45:46 Error: Error indexing mbox file /home/chunyang/Mail//Sent: LF not found where expected etc etc -- ******************************************************************* ** Eef Hartman, Delft University of Technology, dept. SSC/ICT ** ** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-278 82525 ** *******************************************************************
From: Aaron W. Hsu on 27 Nov 2009 10:11 Lew Pitcher <lewpitcher(a)lewpitcher.ca> writes: >Mike Jones <Not(a)arizona.bay> trolled: > >> My point in a nutshell. I'm not a sysadmin. I'm an enthusiastic dabbler. >Exactly. You are a hobbyist, as is everyone who posts to this ng >who is below the age of 35. Those older than 35 probably learned >unix on a real system and slackware when there were few linux >alternatives. Humph. Says you. Aaron W. Hsu
From: Aaron W. Hsu on 27 Nov 2009 10:13
Lew Pitcher <lewpitcher(a)lewpitcher.ca> writes: >That is where you should be using ex, not ed. ed edits basic >streams editor while ex is a basic text editor. Try typing "vi" >from ex and ed to see the difference. No, I mean, quite intentionally, ed. Ex is a line oriented mode of the vi "suite" if you want to call it that, but I meant ed. Ex is mostly functionally equivalent at that point, but sometimes, you don't have access to Vi/Ex. :-) Aaron W. Hsu |