| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
Comments:
<0> VIm_Enforcer: (got your point.) but no please no, not the editor wars all over again...
<1> i am on linux
<2> Alija_: why the disgusing drive names then
<2> NFS?
<3> PayphoneEd: you know, you can just start emacs and go ahead and type too
<4> Alija_ at this point, i'd just mount the floppy and use it normally
<4> mcopy doesn't seem to be working
<1> ok.
<5> koala_man: Yeah, but I don't want to have to press twenty keys at once to save my file
<5> Then another thirty to exit the editor
<4> oh, and you'd probably have to be root to do either.. you know this of course
<3> PayphoneEd: ctrl-x ctrl-s, it's not more keys at once than nano
<1> kevin, i would be able to use/open that file on windows later ?
<4> yes
<2> PayphoneEd: ESC, ZZ
<2> not too hard
<4> make sure you use vfat or msdos fs though
<5> koala_man: Also, why whould I use a bloated editor instead of a nice tiny one?
<4> not ext3 or something
<2> ...
<2> cause nano ****S ***.
<3> PayphoneEd: that, at least, is a valid argument. and the answer is vim.
<2> yes.
<2> cause nano ****S ***.
<2> dont make me repeat taht again
<5> koala_man: Invalid answer, as vi requires me to remember and stumble around with stupid editing commands
<2> its not a hard task, you know, just press up and enter
<5> I don't want to have to reference the manual page just to use the editor
<1> vim_enforcer, wata fak ar ju talking about
<5> Sure, I'll learn it eventually, but why bother when I have something else that just works?
<2> PayphoneEd: you are stupid, and not the commands, if you can't memorize them
<3> PayphoneEd: two commands, yes. i and ZZ
<5> VIm_Enforcer: To be honest, I haven't tried yet
<6> PayphoneEd: i feel where ya coming from....
<2> PayphoneEd: cause nothing can beat the effectiveness of vim?
<5> I know I can memorize them, I just don't feel like bothering with it
<2> koala_man: you've just typed 'ZZ'
<1> thanks guys..have a nice day
<2> :P
<2> Alija_: btw what was that language before?
<2> :)
<1> hehe ;)
<5> Also, the last vi I used was some old-*** one
<1> i was just joking a bit.. ;)
<2> ...
<3> vi ****s, vim is the good stuff
<1> i like to use that expression
<5> That may have something to do with it
<1> heh
<2> PayphoneEd: UNIX is old-***ed too.
<2> still, we use it
<3> who memorizes vim commands anyways
<2> i do
<3> frek
<2> no
<3> damn a-key
<5> VIm_Enforcer: I dunno about you, but I use Linux
<2> enlightened head
<3> you just use them and if they're nice, they stick
<2> PayphoneEd: which is an implementation of unix
<5> It's a Unix clone
<2> yeap
<6> not everyone wants to learn how to insert text in a file... thats the prob with *nix , we expect new users to become super hackers when all they want to do is save a file...
<2> clone == exact copy
<2> :P
<5> It's not exact
<2> there goes your mega super argument
<5> At least I'm making sense
<5> I'm also not starting a huge fight over what editor to use
<2> i am not
<5> See, I switched to Linux so I'd have choices
<4> fight about distros, it's more interesting
<5> I use what I like
<3> I run notepad in wine
<4> koala_man !
<2> <enter>
<2> the soothing vi pleases me
<6> i use editpad in linux
<5> I do need to learn vi commands for when I use old Unix/Unix-like OSes
<5> Or even modern ones
<2> meh
<5> Stupid FreeBSD comes with vi and uses it as it's default
<4> vi always has some key problems whenever I try to use it
<4> like backspace doesn't work
<4> or other random stuffs
<2> meh
<2> it's not vim's fault
<5> I haven't bothered reading the man page for it, so I stumble around with all the : commands and **** like that
<2> it's the terminal's
<4> other editors figure it out somehow :/
<2> PayphoneEd: that means you've been using ex
<5> Well, that one ****s then
<2> which is also a good editor
<5> They almost all use that ****
<2> PayphoneEd: ever used sed?
<5> VIm_Enforcer: Yes
<4> vi has :commands too
<2> cause that a stream version of ed
<2> Kevin`: that's ex mode
<5> That ex mode ****s
<2> no
<2> you can do magic with it
<7> time and place for everything
<2> in a few keydtrokes
<2> strokes
<4> i've seen somone do that magic, heh
<2> like?
<4> applying some change to every line in a file
<4> I forget what
<8> sounds stupid but: is there a way to restore a file, that was removed with rm -r -f ?!
<2> Kevin`: sed
<4> but it looked cool
<8> without r
<5> That's what sed is for
<0> theoretically you can do anything with sed. it's a state machine after all.
<4> I don't think it was a search/replace
<4> but ya
<2> mord: of course
<3> echnaton: what fs
<2> cause it's an editor after all
<8> ext3
<3> echnaton: then no
<2> though a stream one
<5> I used sed to rip all the #pragma once lines out of the MAME source code once
<2> non-interactive
<2> once?
<2> heh
<8> sh*t koala_man :)
<2> you must use it daily to love it
<0> VIm_Enforcer: but it fulfills the requirements of being an universal turing machine pretty well :)
<5> VIm_Enforcer: I already love sed
<8> it was a source code i have been working on the whole day :(
<4> echnaton stop now, unmount the filesystem, and search the hard drive for it
<3> VIm_Enforcer: there's a limit to how often you want to remove pragma lines from the mame source
<2> echnaton: watch your rm -f'ing
<2> that's all i can tell
<2> :|
<5> What I do with the sources is...
<8> rm -fiing ?!
<5> I take the MAMEW source, stick the OSD part from XMAME into it
<8> VIm_Enforcer, you are right
<4> echnaton less /dev/hda
<2> koala_man: you can use sed not only for the pragma lines
<5> Then I apply the u patches
<4> /line from file
<4> hehe
<5> So I have an XMAME with u patches applied
<2> cool
Return to
#linux
or
Go to some related
logs:
#lisp
#css
windowmaker modular-x
Access denied for user 'mailsql'@'localhost' (using password: YES)
exim rfc3463
#linux
Chuck Norris gets beat up
sudo but not su
#suse
system error code 3027
|
|