IRC Logs

Network: freenode Channel: #vim

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

[19:50]<znzumnz_>so on vim, i just do vim -T xterm-256color
[19:50]<znzumnz_>myren: no
[19:50]<pfrsdrhh>phrakture: well, spell checking is for natural language, isnt it?
[19:50]<lxzzcvuzn>myren: no, just the right terminfo setting
[19:50]<lxzzcvuzn>PlasmaHH: aye... IIRC comments are assumed to be something like /* This is a comment, and it's spelled right */
[19:51]<pfrsdrhh>phrakture: hmk. they should have made it configurable somehow... I just patched my doxygen.vim file to have spell checking there
[19:51]<lxzzcvuzn>not /* prbchk xmc 1124: sgnedoff johnx fxbug
[19:51]<lxzzcvuzn>PlasmaHH: normal language files should have spell checking in comments by default
[19:51]<ddzgg>ah, you have to set screen to be 256 color aware
[19:51]<lxzzcvuzn>myren: screen is different
[19:51]<lxzzcvuzn>you said xterm
[19:51]<ddzgg>indeed
[19:52]<ddzgg>just pointing this out, in case anyone else is poking along too
[19:52]<eddgdw>PlasmaHH: he sits rigth next to me, he is not joking
[19:52]<eddgdw>PlasmaHH: he's got UNDU at ctr-z
[19:53]<pfrsdrhh>undu? well, then his terminal supports it, but usually its the terminal app that catches it and sends a SIGSTOP to the process
[19:53]<pfrsdrhh>phrakture: when having syntax=cpp.doxygen there is spellchecking within strings, normal comments, but not for doxygen-style comments, which was a bit inconsistent so i enabled it here for me, with a dirty :%s/contains=/&@Spell/g
[19:54]<lxzzcvuzn>hrm...
[19:56]<ddzgg>anyone know where i can get a port of textmate's default "twilight" color scheme?
[19:56]<ddzgg>frakking badass
[19:56]<rrdgssrg>jed doesn't catch ^Z here.
[19:57]<rrdgssrg>it uses ^_ for undo
[19:58]<pfrsdrhh>hm, the latex highlighting/spell checking stuff should somehow note that \emph{P}lugin is Plugin and not P lugin ...
[19:59]<txnsxnnl>PlasmaHH: why would you use something like that?
[19:59]<pfrsdrhh>TheSheep: in a footnote to explain some abbrevation that is not formed only out of the starting letters
[19:59]<txnsxnnl>ah
[20:00]<txnsxnnl>I was afraid you were highlighting the first letter of the paragraph %)
[20:01]<pfrsdrhh>I think asking it to accept something like \somecmd{...}{ACL}{...}{..}s to be ACLs is too much to ask for ;)
[20:03]<txnsxnnl>PlasmaHH: especially when it has no way of telling what the part in {} does
[20:04]<pfrsdrhh>yeah, hehe
[20:04]<pfrsdrhh>unless of course you add a complete tex parser ;)
[20:06]<ddzgg>grr, i think uxterm is only operating in 88 color mode or something
[20:06]<lnjnnzm>Quite possibly... For a long time, xterm in debian wasn't compiled with 88- or 256 colour modes
[20:06]<pfrsdrhh>I seriously wonder why you would need so much colors in a terminal. its a terminal. not a video player.
[20:06]<txnsxnnl>4 coulours is plenty
[20:06]<vyavjzy>bitchx that is why ;-P
[20:07]<lnjnnzm>PlasmaHH: syntax highlighting...
[20:10]<lnjnnzm>Try without screen first... try a plain xterm with vim running in it
[20:10]<ddzgg>yeah, works fine sans-screen
[20:10]<lnjnnzm>screen can get in the way with issues like this - best to get either side working first
[20:21]<dy>hi, i like the new spellchecking feature in vim. how can I set it so it only spell checks comments in source code files?
[20:22]<pfrsdrhh>hm, it should only spell check comments and strings...
[20:25]<dy>in a .py file it pretty much checks everything
[20:26]<dy>for example 'try' is highlighted, %s is highlighted
[20:26]<dy>variable names are highlighted
[20:26]<dy>PlasmaHH: i'm turning it on using 'set spell'
[20:27]<pfrsdrhh>hm, no idea here... maybe someone else knows, as it should (tm) not do that ;)
[20:30]<rrdgssrg>Python's syntax file doesn't specify anything related to spelling, so everything is spell checked
[20:31]<dy>ah i see
[20:32]<pfrsdrhh>jamessan: any idea how I could try that inkpot scheme?
[20:32]<rrdgssrg>PlasmaHH: use a term that supports 88/256 colors or use gvim
[20:33]<pfrsdrhh>jamessan: I have no idea whether the terms I have do ;)
[20:33]<rrdgssrg>PlasmaHH: if they're urxvt or xterm they probably do. otherwise, they probably don't
[20:34]<lxzzcvuzn>use inkpot in urxvt
[20:34]<lxzzcvuzn>it's superior
[20:34]<pfrsdrhh>well xterm does not seem to, as it turns black on white when I enable that scheme, though the manpage says it does support
[20:34]<lxzzcvuzn>PlasmaHH: TERM=xterm-256color vim
[21:10]<p2g>how can I use vim to insert a string at the beginning of every line?
[21:10]<lnjnnzm>Replace the beginning-of-line marker ^
[21:11]<ddzgg>holy mother of god
[21:20]<ddzgg>jamessan: odd, its not in /etc/terminfo/x/
[22:34]<lxzzcvuzn>stockholm: you should probably ask a real questions - lead-in questions are not good for IRC
[22:34]<xgg0g>Iabbr fld <C-o>:set formatoptions-=r noautoindent<cr>// {{{ <:description><cr><cr><><cr><cr>// }}}<C-o>:set formatoptions+=r autoindent<cr>
[22:35]<xgg0g>question - i want to turn that into a function - how do i return that string from a function?
[22:35]<xgg0g>So i have something like
[22:35]<xgg0g>Iabbr fld CreateFold()
[22:35]<xgg0g>hmmm
[22:36]<pfrsdrhh>phrakture: what windowmanager/desktop environment do you use?
[22:36]<xgg0g>yeah, that is what i wanted

Back to #vim
Or go to some related logs:
#gentoo
#gentoo
#debian
#ubuntu
#cisco