Re: Time to remove naming restrictions?
On 10/1/06, Bram Moolenaar [EMAIL PROTECTED] wrote: Nikolai Weibull wrote: One thing that really annoys me with Vim is the limits it emposes on what names are legal for user-defined functions and commands. I know the reason for these restrictions, but I don't think they make much sense, especially so for user-defined commands. I realize that overriding :quit does have its implications, but done carefully, this does allow for some interesting effects. So, why not lift the restrictions on valid names for user-defined functions and commands? That is, give me good reasons for why they should be maintained and I'll drop this request. Predictability. As in what? That :quit always works as documented? Sure, that's great, but if that's the problem, the restriction should be limited to commands already defined. And what happens when more commands are added? Hell, then they'll break the user-defined commands with the same name. Big deal; that's life, you'll get over it - everyone does, eventually. I really don't see the big difference between user-defined commands clashing with built-in commands and user-defined commands clashing with each other. It'll happen; unless you start adding prefixes or namespaces or some other way of separating your commands. But then you lose out on simplicity. You don't want to type :NOWCommand (given that NOW is my prefix), and I don't want to type :Command; I want to type :command. Sure, it only saves my fingers from giving up on me for so long, but every little bit helps. I guess my problem is that I want - and I've always wanted - the flexibility of Emacs coupled with the simplicity and efficiency of Vim's command set and modes. I guess that's why I nitpick at things such as this. nikolai
Fwd: Do Not Reply To This Message:Re: Time to remove naming restrictions?
I keep getting this f**king message every time I post to vim-dev. Seriously, wtf? nikolai (awaiting another notification for this mail not getting through) -- Forwarded message -- From: System Administrator [EMAIL PROTECTED] Date: 2 Oct 2006 14:19:05 -0400 Subject: Do Not Reply To This Message:Re: Time to remove naming restrictions? To: Nikolai Weibull [EMAIL PROTECTED] You have reached an email address at KNBT that is unavailable or no longer valid. If you have any questions please call our customer service number at 1-800-996-2062 (toll-free), Monday – Friday: 7:00 a.m. - 7:00 p.m. and Saturday: 8:00 a.m. - 2:00 p.m. Thank You, We are very sorry for any inconvenience. KNBT Banking, Insurance, Investments, Trust [EMAIL PROTECTED] Office: Fax: http://www.knbt.com This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the system manager. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Keystone Nazareth Bank Trust. Finally, the recipient should check this e-mail and any attachments for the presence of viruses. Keystone Nazareth Bank Trust accepts no liability for any damage caused by any virus transmitted by this e-mail.
Re: Searching for selected text
Bram Moolenaar wrote: Matt Mzyzik wrote: I don't like this one more, but it's a good alternative: g/ g? Also, I feel that one day might do something in visual; at least visual line mode. g? is already used for rot13 encoding. g/ is scheduled to be used to search inside the selected area Hmm -- g/ sounds a lot like vis.vim's :S command for searching a visual block for a pattern. It works with V, v, and ctrl-v type visual blocks. Regards, Chip Campbell
Re: Do Not Reply To This Message:Re: Time to remove naming restrictions?
On 10/2/06, Yakov Lerner [EMAIL PROTECTED] wrote: Me too. I think it means that (1) email address at KNBT that is unavailable or no longer valid, and (2) it's time for you to add special filtering rule to your mail reader. I mean, who said mail bot cannot post to mailing list ? It's not posting to the mailing list, it's sending it to me, and I haven't asked for a return receipt or anything. One would hope that mailing list software + MTAs would get together and understand that I, the poster to the mailing list, don't want to know that some douchebag registered an email address with the mailing list and didn't remove themself from the mailing list when it was dropped at the recipient end. Also, it would be nice if the MTA in question would only send /one/ notification (during a given time period), not once every time. So anyway, I guess my request is for Felix von Leitner, or whoever doesn't maintain this mailing list anymore (according to earlier discussions on similar subjects), to remove the offending email address from the mailing address. Thanks. nikolai P.S. Sorry about the extra traffic about this. D.S.
Re: Autocommand-Event for Clipboard-Changed
Suresh Govindachar wrote: Is it possible to add an autocommand-event for Clipboard Changed? Not really. This is not something that happens inside Vim. Polling for changes in the system is not really something I would like to add to Vim. -- Managers are like cats in a litter box. They instinctively shuffle things around to conceal what they've done. (Scott Adams - The Dilbert principle) /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: gvim segfaulting on Solaris 10
Ali Akcaagac wrote: On Sun, 2006-10-01 at 23:13 +0200, Bram Moolenaar wrote: The bonobo stuff is only used when compiling for GTK 2 with Gnome support. I generally discourage compiling with Gnome, it has its problems. This is mentioned in the Makefile. If you compile without Gnome, which is the default, no bonobo stuff is used by Vim. If a bonobo library is still linked in then it's because of a dependency. I do understand this. But what I tried explaining was that BonoboUI is deprecated. That means it's dead stuff from within GNOME which should not be used anymore (from what the developers say). So basicly there is no need for extra GNOME GUI components anymore since the encouraged and recommended way to do GNOME GUI is by using GTK+ GUI (from what the developers say). The only interesting part therefore remains is the session management. Perhaps someone who knows the details about Gnome can make the changes, test it and send us a patch? Obviously I don't have time to learn the proper use of Gnome libraries. -- The acknowledged parents of reengineering are Michael Hammer and James Champy. When I say they're the parents I don't mean they had sex - and I apologize for making you think about it. I mean they wrote the best-selling business book _Reengineering the Corporation_, which was published in 1993. Businesses flocked to reengineering like frat boys to a drunken cheerleader. (This analogy wasn't necessary, but I'm trying to get my mind off that Hammer and Champy thing.) (Scott Adams - The Dilbert principle) /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
CursorHold when cursor is in command-line
I observe that CursorHold is not triggered when cursor in spending long time in commandline, correct ? Is it possible to trigger CursorHold also when cursor is in command line ? (Maybe by some :au CursorHold commandline syntax ?) BTW does all this mean that if I enter commandline (:) within less than 'updatetime' from last change, .swp file is not updated all the time I am still in commandline ? Yakov
