ping Slack dev team
in [Slackware]
|
Prev: LewPitcher.ca tops Google Search!
Next: Xorg and Intel Integrated Graphics Chipset: low resolution
From: Henrik Carlqvist on 27 Nov 2009 02:21 Sylvain Robitaille <syl(a)alcor.concordia.ca> wrote: > Then I saw colleagues doing some things with vim that I'd been wishing > I could figure out how to do with Emacs Even though this thread has since long left its initial purpose I get curios. Do you have any quick example of some of those things vi can do? regards Henrik (who only knows how to use vi for basic editing and mostly uses emacs) -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: root(a)localhost postmaster(a)localhost
From: Henrik Carlqvist on 27 Nov 2009 02:28 Mike Jones <Not(a)Arizona.Bay> wrote: >> PS: the ls, rm, cp and e.g. grep and gunzip commands are in busybox too, >> Pat _is_ using a separate "tar" executable, but there is a minimal tar >> in busybox too). > Ah. This is a different situation to just sticking a text editor into a > dir then. Yes, but the fact that most commands are built into busybox does not mean that all commands have to be there. If you want some extra commands you can put some files in the initrd as I wrote earlier. However, it might not be enough to only put an executable file there, you might need some dynamic libraries also. And yes, the more "bloat" a wanted feature needs in the standard install disk the less likelyhood that it will pass Pats final word on the decision whether it will be included. regards Henrik -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: root(a)localhost postmaster(a)localhost
From: Grant on 27 Nov 2009 04:04 On Fri, 27 Nov 2009 08:28:31 +0100, Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote: >Mike Jones <Not(a)Arizona.Bay> wrote: >>> PS: the ls, rm, cp and e.g. grep and gunzip commands are in busybox too, >>> Pat _is_ using a separate "tar" executable, but there is a minimal tar >>> in busybox too). > >> Ah. This is a different situation to just sticking a text editor into a >> dir then. > >Yes, but the fact that most commands are built into busybox does not mean >that all commands have to be there. If you want some extra commands you >can put some files in the initrd as I wrote earlier. However, it might not >be enough to only put an executable file there, you might need some >dynamic libraries also. Perhaps a static-linked version of the desired binary? But I would think most people spend very little time in the installer. I met vi same time I met unix -- there's less than a dozen keystrokes to be learned for basic editing, I don't see the hassle in remembering that. And one's left little finger soon streches the extra inches needed to reach the escape key ;^) I usually rewrite /mnt/etc/lilo.conf during each new install, but leave editing /etc/fstab and other .conf files until after the first boot. On a new system first things copied from the file server (once I get nfs access) are custom .vimrc and .bash* files, the ~/.ssh/authorized_keys for root and user, and my kernel build scripts. Then I have vim tamed, and only meet vi in its other roles as 'crontab -e' and visudo -- what do the nano, pica people do here? Grant. -- http://bugsplatter.id.au
From: Helmut Hullen on 27 Nov 2009 04:39 Hallo, Grant, Du meintest am 27.11.09: > Then I have vim tamed, and only meet vi in its other roles as > 'crontab -e' and visudo -- what do the nano, pica people do here? a) a definition VISUAL=/bin/mcedit EDITOR=/bin/mcedit export VISUAL EDITOR in "/etc/profile.d" and/or "~/.profile" or b) VISUAL=/usr/bin/mcedit crontab -e VISUAL=/bin/ed visudo VISUAL=/usr/bin/nano vipw on the CLI. If "VISUAL" is not set as an environment variable you can use EDITOR=/usr/bin/mcedit crontab -e etc. on the CLI. Maybe you have to define Defaults editor=/usr/bin/mcedit /usr/bin/nano /bin/ed Defaults env_editor in your "/etc/sudoers". Viele Gruesse Helmut "Ubuntu" - an African word, meaning "Slackware is too hard for me".
From: Grant on 27 Nov 2009 05:57
On 27 Nov 2009 10:39:00 +0100, helmut(a)hullen.de (Helmut Hullen) wrote: >Hallo, Grant, > >Du meintest am 27.11.09: > >> Then I have vim tamed, and only meet vi in its other roles as >> 'crontab -e' and visudo -- what do the nano, pica people do here? > >a) a definition > VISUAL=/bin/mcedit > EDITOR=/bin/mcedit > export VISUAL EDITOR > >in "/etc/profile.d" and/or "~/.profile" > >or > >b) > > VISUAL=/usr/bin/mcedit crontab -e > VISUAL=/bin/ed visudo > VISUAL=/usr/bin/nano vipw > >on the CLI. > >If "VISUAL" is not set as an environment variable you can use > > EDITOR=/usr/bin/mcedit crontab -e 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 mcedit /usr/bin/mcedit This leaves me a bit doubtful now about the other vi alternatives you gave? > >etc. on the CLI. > >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? Each to their own :) Grant. -- http://bugsplatter.id.au |