clewn inclusion?
hi everyone, I was wondering how likely inclusion of the clewn[1] project in vim would be? I have to admit I have no idea how deep the changes are and if the patches include any evil hacks.. What I do know is that it seems to do a pretty good job at making gdb a bit more usable by incorporating it in my editor of choice. So what's with that ? regards, Tobi [1] http://clewn.sourceforge.net/
Re: clewn inclusion?
Am Donnerstag, den 12.04.2007, 17:18 +0200 schrieb Tobias Pflug: hi everyone, I was wondering how likely inclusion of the clewn[1] project in vim would be? I have to admit I have no idea how deep the changes are and if the patches include any evil hacks.. What I do know is that it seems to do a pretty good job at making gdb a bit more usable by incorporating it in my editor of choice. So what's with that ? regards, Tobi [1] http://clewn.sourceforge.net/ Stupid me.. obviously I wanted to referto vimgdb and not clewn. clewn is an external solution, vimgdb is a vim patch..
Re: VimTips Wiki: New Direction
On Tue, 2007-03-06 at 18:38 +0200, Ali Polatel wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Zdenek Sekera ([EMAIL PROTECTED]) wrote: -Original Message- From: Spencer Collyer [mailto:[EMAIL PROTECTED] Sent: 06 March 2007 08:31 Cc: Vim Mailing List Subject: Re: VimTips Wiki: New Direction On Tue, 6 Mar 2007 03:18:13 +0200, Ali Polatel wrote: And check out http://en.wikibooks.org/wiki/Learning_the_vi_editor/Vim/TipsSandbox to see how it parsed tip #1. Looks good. Only comment I have is it might be better if the 'By' and 'On' lines for the comments were on the same line. Anything that allows more useful info on a screen at once is an improvement in my eyes. Done. Yes, I very much agree, use screen real estate for useful info as much as possible. Otherwise good IMHO! If I might add my impression: Generally I think it is indeed quite likable. Just some thoughts : Looking at : http://en.wikibooks.org/wiki/Learning_the_vi_editor/Vim/TipsSandbox/Tip_1:_the_super_star my thoughts: 1. focus/structure: At the moment there is a bit of a lack of focus when I look at the page. The eye-catcher is more or less the box with the author/creator/etc meta information. The focus should however be on the actual text/body of the tip. So maybe the text should be in a (differently colored?) box to gain more attention and separate it from comments and meta info etc. Same goes with the info boxes for comments on the tip and the comments contents. I'd also suggest to maybe separate tips with horizontal lines (maybe even removing the info boxes..) Also what about perhaps indenting the comments a bit to the right? 2. formatting: I think tex is right with its default formatting in which line length is rather short. I think it would be nice if line breaks could be added ? However while typing this I realize that this would suck when you break up code.. I realize that currently it's still about figuring out how to properly parse/convert the content etc.. just wanted to shout out what I have on my mind about it. thanks to those doing all the work, looking forward to use the wiki-tips already.. regards, Tobi
Re: tips project
On Fri, 2007-02-23 at 09:46 -0600, Tom Purl wrote: Ok everyone, the project's created: * http://code.google.com/p/vimtips/ I think there's a major disadvantage in using the code.google.com wiki - it only allows people who have been added to the project to edit the wiki via the web interface (please correct me if I'm wrong). At least if it allows editing by anyone with a google id, that would be reasonable enough for anyone to contribute and it'll avoid spam, but if only people added to the project can edit the wiki, it'll become a bottleneck and will discourage anyone who wants to contribute, I don't think many people will go through that much trouble (at least going by the number of 'anonymous' tip notes). I agree that this could be a problem. It could be lessened somewhat if Google allowed people to join the project using a web interface, but they don't. On the help site (http://code.google.com/support/bin/answer.py?answer=56534topic=10382), they recommend that you email one of the project members to gain access, which they would allow you to create and edit wiki pages. But this is awkward and slow at best. To make things a little easier, I'll create a mailing list on the project that people can use to request access and make miscellaneous comments. Hopefully this will be a decent workaround until Google gives us finer-tuned control over the project's security. Okay, so now I am really an outsider to this whole issue as in that I have just been following the whole thread with interest because i regularly check vim tips/scripts at vim.org ... But now I am a bit confused how things are moving on to the google wiki because I somehow assumed that most people discussing which wiki to pick were against the google wiki for various reasons, and in special the reason that swaroop just brought up again (sign-up troubles). SPAM-Countermeasures are good..as long as they are not contra-productive and affecting user experience in a bad way. Why did things suddenly turn in favor of google again? And is it just me or is the google wiki design not exactly very pleasing to the eye.. I hope this mail isn't too inappropriate in that I just sit there and do nothing and then suddenly start to moan. I just want to understand motivations here.. and looking at the google wiki and at the old vim tips I just somehow don't see this really happening (from a user/vimtips contributors point of view.. enough smart people contributing conversion/import scripts are there alright! vim crowd /is/ smart :) best regards, Tobi
Re: cindent weirdness
Looks lika a misbehaving sript. In the problem buffer (if and when the error reappears): :verbose setlocal cindent? cinoptions? indentexpr? - 'cinoptions' influences how 'cindent' works - if 'indentexpr' is nonempty, it overrules 'cindent'. :verbose will tell you where each of these options was last set. It just happened again right now. So here is the result of your suggested command: cindent Last set from /usr/share/vim/vim70/indent/c.vim cinoptions= indentexpr=GetTexIndent() Last set from ~/shared_home/vim/plugin/indent/tex.vim So I suppose it might be tex.vim screwing things up there ?
cindent weirdness
Hi, I am having some problems with cindent. I was busy coding when suddenly indenting stopped working. cindent is set (echo cindent - 1). The odd thing is that it only stopped working on one buffer. How does that make sense? After I closed the buffer and reopened the file it worked again. This happened before but unfortunately I don't have the slightest idea how to reproduce it. Any ideas on this? regards, Tobi
vsplit spanning over all buffers
hi all, short question that I couldn't answer myself using the vim help.. How can I get a vertical split that spans over all previously opened buffers? (like a 'side pane' sort of thing) ? thanks for any help.. regards, Tobi
popupmenus in textmode
Hi, I was wondering if someone could give me some hints on creating/using popup menues in scripts such as those used for omnicomplete ? I had a look at what I could find in vim help but somehow did not get very far. Maybe someone could give me a mini example on how to create a menu with some entries and how to call it ? That'd be great. regards, Tobi
