IRC Logs

Network: freenode Channel: #vim

	Enter your search terms Submit search form
	Web www.irclog.org

[00:51]<t`>how do i disable wrapping of sentenses in vim when editing python?
[00:52]<t`>for C it wraps them whenver it hits 80 or so chars i think.. but it also does taht with python which is annoying :/
[00:55]<cnzrjvx>T`: autocmd FileType python setlocal fo-= t, or so
[00:55]<cnzrjvx>see :h tw and :h formatoptions
[00:57]<rvfjgmjgj>lines of more than 80 _are_ annoying
[00:58]<rvfjgmjgj>s/80/& characters
[00:59]<_urfd>what types of problems would cause <C-Up>, <C-Down>, etc, to not actually get mapped unless i use C-v (insert mode) and insert in the control seq that get generated?
[00:59]<t`>kergoth, thanks
[01:00]<t`>setlocal tw=0 does the job there
[01:08]<cnzrjvx>T`: well, tw can be useful for more. for example, if t is not in fo, but c is, itll use tw to wrap the text in your comments, but not elsewhere.
[01:09]<cnzrjvx>T`: which is why i suggested just removing t from formatoptions
[01:36]<p2znm>Hey! I wonder if anyknow knows the default keybinding for :cnext, or where I can find a list over default keybindings?
[01:38]<wjjmsmjr>i work with bind zone files quite a bit. Is there ways for VIM to do mathematical funtions on text?
[01:38]<wjjmsmjr>i know control-a and control-x will increment/decrement
[01:38]<wjjmsmjr>but i'd like to create a series of numbers...if that makes sense
[01:38]<2jrrd>visinc
[01:39]<wjjmsmjr>what's that? :he visinc?
[01:39]<ndjwy>WoodsDog: create a macro if it's arithmetic series
[01:39]<2jrrd>it's an addon: visincr
[01:39]<ndjwy>fbred: there's none afaik, and you can find them in help
[01:39]<wjjmsmjr>let me check that out...
[01:40]<wjjmsmjr>that could be sweet.
[01:40]<2jrrd>it's a great tool. i use it every couple days
[01:41]<2jrrd>you highlight a column and it sequences it into numbers for you
[01:41]<wjjmsmjr>i'm going to try it out
[01:41]<wjjmsmjr>that could help me a great deal
[01:42]<p2znm>Nyoxi, :h what?
[01:43]<ndjwy>fbred: what exactly?
[01:43]<p2znm>under what topic can I find the default key-bindings?
[01:44]<ndjwy>you mean bindings to : commands?
[01:44]<p2znm>yep
[01:44]<ndjwy>I can't think of nothing in particular, usualy near the command itself
[01:45]<p2znm>hm.. ok, i really think it is a default binding, I just can't seem to find it
[01:46]<p2znm>but i'll just add my own, thanks for the help though :)
[01:48]<wjjmsmjr>whoa boggy! that's going to work nicely!
[01:48]<2jrrd>;p
[01:50]<wjjmsmjr>it'd be cool if you could highlight text, andit would jump to the first number and start incrementing there
[01:51]<zusnz> ctrl+x ctrl+a ?
[01:52]<wjjmsmjr>i guess i could do that..just get a macro to do it a bunch of times
[01:52]<zusnz>#^x would repeat it number of times, no?
[01:53]<wjjmsmjr>would that increment it from where it left off? or just increment all lines by one?
[01:55]<-- sgvgzs xzs fuyv (>/dev/brain")
[02:14]<2jrrd>where it left off
[02:14]<2jrrd>3 asdf
[02:14]<2jrrd>4 adsf
[02:17]<slnsxrc>i too have always thought that incrementing from where it left off would be great
[02:20]<2jrrd>visincr starts with the first, but doesn't change it
[02:28]<cered_mrg>How can I set ctrl-tab to switch between tabs (I know it uses the map command, but I don't know the identifiers for ctrl-tab and page-up and page-down)?
[08:10]<saxyed_>question: how can i get vim to do a load line where it puts the entire directory in by default on the line, so you can quickly go up directories etc...very similar to the default emacs way of doing it. I"m so used to that that the current way is painful, and the various "tree" traversal ways it has for loading are equivalently painful. I want fast and simple :)
[08:11]<rrdgssrg>that doesn't make sense
[08:11]<saxyed_>sure it does :)
[08:12]<rrdgssrg>no, it doesn't. I can't begin to offer help if I can't understand what you're asking for
[08:12]<mgzdgy>What's a "load line"?
[08:12]<saxyed_>example I'd like "e:" to fill in c:\perforce\project_branch\sports\packages\dev\source\ai\ if that is the current dir. Right now I have it defaulting to loading from the current dir via %:h but that's not enough
[08:13]<saxyed_>so that i can quickly hit ctrl-w to go up 3 directories
[08:13]<saxyed_>then type and tab match to back down three more
[08:13]<saxyed_>ie. exactly how the default emacs load command line does it
[08:13]<rrdgssrg>hint: most of us have no clue what emacs does
[08:13]<rrdgssrg>so, using that as an example is useless
[08:13]<saxyed_>right now if im down deep and i hit :e I have to do ../../../../ and try to guess how many up i have to go
[08:14]<saxyed_>and i dont want to default to the top because it's equivalently far down
[08:14]<saxyed_>ah, i figured most people would want to be fluent in a few editors
[08:14]<saxyed_>that's why im relearning vim after a 10 year hiatus :) got fluent in emacs, trying out vim now
[08:14]<saxyed_>almost there for day to day development at work, but the lack of a fast way to load files is very painful
[08:15]<saxyed_>so basically, if CWD is a certain directory structure, I'd like for :e to fill that in for me automatically
[08:15]<saxyed_>ie. automatically print out %:h
[08:15]<rrdgssrg>yeah, I understand now
[08:15]<rrdgssrg>just trying to think of a way to do it
[08:15]<saxyed_>aye
[08:16]<saxyed_>a lot of files i load with tags done with --extra=+f, but there are 230,000 total files in my project
[08:16]<saxyed_>so they all aren't tagged needless to say ;)
[08:16]<saxyed_>so i do a lot of directory traversal
[08:18]<rrdgssrg>you could pretty easily have it bring up the file explorer on the current directory and then you could navigate from there
[08:19]<saxyed_>navigating that file explorer is slower than i can do on a command line with ctrl-w and directory name completion though
[08:19]<saxyed_>and btw i mean current directory to mean "the directory that the file in the current buffer resides in"...which %:h gives you, i have that as my default :e
[08:20]<rrdgssrg>that's not what %:h gives you. that's what %:p:h gives you
[08:20]<auga2fjaanz->is there a 'delete other buffers' command?
[08:20]<saxyed_>bdelete #
[08:20]<rrdgssrg>that only deletes the alternate buffer
[08:21]<saxyed_>doesn't that delete buffer #N?
[08:21]<saxyed_>that's how i use it
[08:21]<rrdgssrg>well, the literal 'bdelete #' deletes the alternate buffer ;)
[08:21]<saxyed_>sorry, where # is the buffer number ;)
[08:21]<saxyed_>can you bdelete a range?
[08:21]<saxyed_>perhaps
[08:22]<rrdgssrg>yes
[08:22]<rrdgssrg>:1,3bd
[08:22]<saxyed_>so shouldn't be too tough to write a macro (or a function?) to select all buffer numbers other than the current one and pass that in that form
[08:23]<saxyed_>im still not used to buffers in vim...:bp confuses me as i always expect it to go to the most recently used buffer, instead it goes one down in the number list heh
[08:23]<rrdgssrg>schizm_: you might like bufexplorer
[08:23]<saxyed_>so i get lost and when i have 40-50 files open and i ctagged to where i was i gotta find it again, sometimes C-o works, sometimes it doesn't
[08:23]<saxyed_>ya i have it
[08:23]<saxyed_>but \be then arrowing or searching is slow
[08:24]<rrdgssrg>it's faster to get it right on the first try than to fumble around trying to get it right
[08:24]<saxyed_>if i could be \be then 1 key press, that'd be golden

Back to #vim
Or go to some related logs:
#gentoo
#gentoo
#azureus
#gentoo
#reactos