| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9
Comments:
<0> I opened up QuickSilver, and started to type "Juniper" for some reason (Thinking of a google search at the time)
<1> yea. if you select something it uses the selection buffer. if you cut/copy something it uses the cut buffer. :)
<2> What about shift+insert? :) That's the X way too
<0> And It registered some of the keys and pulled OrngeTide's contact info
<1> xterm tries to sniff around for one or the other when you paste. but if you paste a selection buffer it doesn't "empty" the selection buffer. but if you paste from the cut buffer it pops the entry off.
<3> autocutsel is supopsed to always keep 2 buffers in sync
<1> Maloeran, shift+insert is a wordstar-ism :P
<1> or is it just a dos-ism. i don't remember
<0> I think it's a dosism
<3> it's also Windows3-ism
<1> aedinius, i wonder what i have to do with juniper.
<1> well it's been around way before windows 3
<0> OrngeTide: I think just 'j' and 'n'
<0> WIndows3 started using Ctrl-C/V/X
<1> aedinius, that's a very silly app you have.
<0> OrngeTide: It just guesses, didn't find any other matches here
<0> (It doesn't actually do googles)
<1> yea. ctrl-c/v/x to counter cmd-c/v/x that was already used for years in MacOS. :)
<0> So much nicer
<4> shift-insert came from wordstar eh?
<3> xterm handles it better than kconsole
<1> Jaggy_, maybe not.
<1> the real thing that bugs me about cut buffer versus selection buffer is that i can't think of a better way to do it and still offer the feature that you can select something in one app and paste it into another without doing an extra action.
<1> firefox/mozilla handles the whole thing extremely poorly.
<4> I remember there was some nice smooth flow to editing in windows with ctrl-arrow highlighting, shift, del, etc.
<4> I don't remember what telemate used for highlighting
<1> dos edit.com and turbo vision (turbo pascal / turbo c) had the whole shift+direction and shift+insert thingy
<4> ot, what do you mean "extra" action in this case?
<1> Jaggy_, windows: select, copy-action, paste-action ; x11: select, paste-action
<1> where the -action is ctrl-c/v/x or right click and context menu item
<4> there's something which feels more efficient to shift-move, shift-del, shift-insert
<4> some functionality I lost somewhere along the way
<4> and it's not the same in vi
<1> well if you're using the keyboard, sure.
<4> and it wouldn't be the same on this laptop
<1> i like doing selection in vi. mark, and enter a range for your action. :)
<4> you ever enter a range?
<1> yea. all the time.
<5> I use shift-insert to paste, ctrl-c does bad things :p
<1> :.,'ms/foo/bar/g
<4> what do you put in? I never enter ranges
<3> i use 'a,'b ma mb
<4> I just use the visual selection in vim, it inserts '<,'> when I hit :
<5> Two9A you rockstar
<1> although the . is optional.
<3> my idiom is 'a,'bm. 'a,'bt.
<4> and often I use % .. but that's it
<3> 'a,'bw!file
<4> :%s///
<1> oh. i don't make the second mark. i do it from the cursor position.
<3> when i move/copy, i make target my current pos
<1> i use ,$s/foo/bar/g occationally.
<4> I use ma 'a a lot
<1> Aeon_, i usually just do mm<move to position>d'm<move to postion>p to do cut/paste.
<4> in insert mode I have mappings of `sequences for editing
<1> or y if i want to do copy.
<1> vim has a nice interactive selection mode. and it can do block selection which is really nice (but not as powerful as the block select in 'screen')
<4> www.voyager.com/GotoFileArg.vim
<1> but i never use vim if i can avoid it.
<3> i use vim but i never use its visual selections
<1> vim should have been called vinv (vinv is not vi)
<3> and vim can handle mouse in xterm
<3> i don't use mouse in xterm, too
<3> OT: vim is totally backward-compatible with vi
<1> yea. i never use the appmouse feature in xterm, i actually disable it because it's annoying in links.
<2> Ew, I never touch a mouse except to browse
<1> Aeon_, it is totally not backwardly compatible with real vi
<3> OT_: vim even preserves bug-for-bug compatibility with historical vi bugs
<1> any nobody on vim.org would even admit that it was *fully* compatible.
<3> @OrngeTide: why not ?
<1> well it's not compatible.
<3> @OrngeTide: why not ?
<1> and it's not supposed to be. it is supposed to be a refined vi interface
<3> OT: vim has this 'set cp/set nocp' option
<3> With 'set cp' (compatible), it's compatible
<3> With 'set nocp' it is not
<1> yea. it is incomplete.
<1> set nocp is default too
<3> no
<4> smart
<3> if there's no file ~/.vmirc, 'set cp' is default
<4> I love my wife, not her grandmother
<3> if you have ~/.vimrc, then this turns 'set nocp' on automatically
<4> well.. I never met her grandmother
<3> what what's good in compatible mode ? you can't even use arrows in insert mode
<4> but I think it's good to get one that matches the times?
<1> Aeon_, well apparently debian has it screwed up because i don't have a .vimrc but i just did :set cp? and it said nocompatible
<4> I want to cry
<3> maybe it comes from /etc/vimrc something
<3> try :verbose set cp?
<1> i don't ever use arrow keys...
<1> i don't even use arrow keys in my shell.
<1> Aeon_, probably. i don't really care to figure it out.
<3> ':verbose set cp?' will tell from where this setting comes from
<1> it's just proof that vim is generally configured not to be vi on distros
<3> maybe it's , when called by name 'vim' vs name 'vim'
<3> *'sim' vs 'vi'
<3> *'vim' vs 'vi'
<1> nvi has a vi-style undo history. which i like a lot better than vim's emacs style.
<3> no undo levels ?
<3> vim has option for this
<1> Aeon_, well it does undo levels in a funny backwardly comaptible way
<1> Aeon_, and the style that it is done in is more in the theme of vi than vim's style is
<1> like undo undoes the undo. but . repeats the undo further. etc
<4> u toggling is probably good.. if there were a way to get further back if you wanted.
<1> obviously you can turn this extension off in nvi. but it's nice and doesn't sacrifice compatibilty terribly.
<4> but it all makes me sad right now
<1> Jaggy_, . gets you further back in nvi and a few other vis.
<3> in vim, this is compatible by :set cpo+=u
<1> Aeon_, doesn't work the same
<3> vi had dozens of options, vim has trillion of options
<3> "u Undo is Vi compatible. See |undo-two-ways|."
<1> Aeon_, yea. that's not the same
<1> you simply are not paying attention.
<3> :help undo-two-ways
<1> accept that vim doesn't emulate and do everything the way I like.
<4> of course :)
<3> vim does not emulate nvi, i agree
<4> OT, WHY NOT CODE YOUR OWN???
<4> ;)
<1> oh i did write my own text editor.
<3> there are couple things in vim that were mimicked from nvi, but fre
<1> but it's not like anyone has my text editor installed
<3> really ?
<3> what is it called
<1> je
<3> je
<3> you dont use it, do you ?
<4> jee
<1> Aeon_, only when i need some obscure text processing.
<1> and it's not installed on the servers at work
<3> OrngeTide: why don't you put it on sf.net
<1> it's too weird to put it in ~/bin/ since i am on both solaris and linux servers. so i'd have to make some kind of shell script to detect the OS and run different binaries. :(
<1> Aeon_, oh i hate sf.net
<1> plus i wanted to merge my editor with 'sc' or maybe just add some spreadsheet features to it.
<3> bbr
<4> I compiled with -pg but it's not making a gmon.out
<4> compiling to .o and the final gcc -o binary *.o are both done with -pg
<4> although the later has -pg at the very end
<1> i think it has to exit normally for a gmoun.out to be written.
<4> it also abides by my program's chdir() :)
<1> oops :)
<1> is there an environment variable you can set or something for gmon.out so you could force it to go into /tmp or whatever you want?
<2> Better debug before profiling :)
<1> Maloeran, no way. who wants to debug when you can optimize!
<1> maybe bugs will go away when you optimize them :)
<0> Oh hey, no cl*** tomorrow
<6> OrngeTide: hey
<3> i can't believe it. single-user desktop linux with 2gb ram. after 7 days of use, all 2GB is used, and 141904MB of swap, too
Return to
#c
or
Go to some related
logs:
#winxp
#beginner
#politics
#mirc
Aimee_Chuhaloff
#windows
suv4x4
#stocks
ftp as hd
#sex
|
|