cream-general Mailing List for Cream (for Vim)
Cream is a free, easy-to-use configuration of the Vim text editor
Brought to you by:
digitect
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(7) |
Nov
(17) |
Dec
(18) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(7) |
Feb
|
Mar
(34) |
Apr
(34) |
May
(3) |
Jun
(9) |
Jul
(29) |
Aug
(22) |
Sep
(36) |
Oct
(43) |
Nov
(15) |
Dec
(3) |
2004 |
Jan
(13) |
Feb
(25) |
Mar
(72) |
Apr
(45) |
May
(47) |
Jun
(36) |
Jul
(25) |
Aug
(33) |
Sep
(22) |
Oct
(68) |
Nov
(58) |
Dec
(30) |
2005 |
Jan
(46) |
Feb
(46) |
Mar
(34) |
Apr
(65) |
May
(24) |
Jun
(13) |
Jul
(12) |
Aug
(21) |
Sep
(19) |
Oct
(12) |
Nov
(25) |
Dec
(65) |
2006 |
Jan
(23) |
Feb
(15) |
Mar
(36) |
Apr
(47) |
May
(47) |
Jun
(51) |
Jul
(23) |
Aug
(14) |
Sep
(23) |
Oct
(47) |
Nov
(33) |
Dec
(10) |
2007 |
Jan
(4) |
Feb
(6) |
Mar
(2) |
Apr
(10) |
May
(27) |
Jun
(8) |
Jul
(12) |
Aug
(52) |
Sep
(17) |
Oct
(7) |
Nov
(3) |
Dec
(42) |
2008 |
Jan
(21) |
Feb
(22) |
Mar
(7) |
Apr
(6) |
May
(13) |
Jun
(5) |
Jul
(4) |
Aug
(5) |
Sep
|
Oct
|
Nov
(22) |
Dec
(4) |
2009 |
Jan
(2) |
Feb
(16) |
Mar
(5) |
Apr
(1) |
May
(6) |
Jun
(3) |
Jul
(6) |
Aug
(8) |
Sep
|
Oct
(36) |
Nov
(4) |
Dec
(4) |
2010 |
Jan
(3) |
Feb
(4) |
Mar
(2) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(2) |
Nov
(1) |
Dec
|
2011 |
Jan
(2) |
Feb
|
Mar
(5) |
Apr
(7) |
May
(14) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(3) |
Jul
(3) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2013 |
Jan
(9) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(7) |
Oct
(5) |
Nov
|
Dec
(2) |
2014 |
Jan
(2) |
Feb
(3) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2016 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Steve H. <dig...@da...> - 2016-04-15 15:19:53
|
On Fri, Apr 15, 2016 at 6:01 AM, Piotr Foltyn <pio...@gm...> wrote: > Hi, > > I'm hitting an issue while using "Cream\Vim" on Windows 10. Say I have > a directory with only two files in it. I right click on "file1.txt" > and from the context menu I select "Edit with Cream/Vim". Predictably, > new "Cream/Vim" window opens up with "file1.txt" loaded - so far so > good. Now I proceed to open the second file so I repeat the above > exercise for the "file2.txt" but this time I'm being hit with a > message saying "Swap file 'c:\blah\.file2.txt.swp' already exists!". > > In essence I'm hitting exactly the same issue as was reported in 2008 > in thread: "Swap file issues when opening multiple files". > > Do you have any idea what might be happening here? I see the same thing on Windows 8.1 and have no idea how to solve this. It's very frustrating, but is obviously something deep in one of Vim's features that not many developer's use. One test you might try: Instead of with the file being edited (default), Cream will place swap files at $CREAM_SWP if it is a valid directory that is writable. Does that make a difference? -- Steve Hall [ digitect dancingpaper com ] Cream for Vim http://cream.SourceForge.net SteveHallArchitecture http://SteveHallArchitecture.com |
From: Piotr F. <pio...@gm...> - 2016-04-15 10:01:35
|
Hi, I'm hitting an issue while using "Cream\Vim" on Windows 10. Say I have a directory with only two files in it. I right click on "file1.txt" and from the context menu I select "Edit with Cream/Vim". Predictably, new "Cream/Vim" window opens up with "file1.txt" loaded - so far so good. Now I proceed to open the second file so I repeat the above exercise for the "file2.txt" but this time I'm being hit with a message saying "Swap file 'c:\blah\.file2.txt.swp' already exists!". In essence I'm hitting exactly the same issue as was reported in 2008 in thread: "Swap file issues when opening multiple files". Do you have any idea what might be happening here? -- Cheers, Piotr Foltyn |
From: Steve H. <dig...@da...> - 2016-03-25 17:28:37
|
On Thu, Mar 24, 2016 at 2:41 PM, Meng Zhu <meng@g.clemson.edu> wrote: > > Thanks Steve. I tried your build and ruby is working fine for the > few commands that I tried in vim. I ran into ruby as I was trying to > make vim/command-t work. but even with your build and ruby22 > installed, I still ran into problems compiling ruby/command-t. so > for now, I decided to go vim/ctrlp which is a lot easier to setup. This sounds like a Vim problem. I'm only compiling default configurations, so it's not anything I can fix other than the build environment/library versions. Vim's Ruby support is still under heavy development, maybe this will improve by the upcoming official 7.5. > also, windows 8.1 blocks your installer, stating that it is from an > unknown publisher or something like that. not sure if this is a > problem, though. I bypassed it by forcing windows to ignore the > signature. I don't know how to get a Microsoft valid key without paying some money and going through extra hoops. Which still doesn't assure anyone of anything. Just more marketing to force money into their ecosystem if you ask me. (Ignore the email bounce, gmail defaulted to the wrong email address on my first email and the list bounced it as unsubscribed. I followed up with a duplicate from the correct account.) -- Steve Hall [ digitect dancingpaper com ] Cream for Vim http://cream.SourceForge.net SteveHallArchitecture http://SteveHallArchitecture.com |
From: Meng Z. <meng@g.clemson.edu> - 2016-03-24 18:41:54
|
Thanks Steve. I tried your build and ruby is working fine for the few commands that I tried in vim. I ran into ruby as I was trying to make vim/command-t work. but even with your build and ruby22 installed, I still ran into problems compiling ruby/command-t. so for now, I decided to go vim/ctrlp which is a lot easier to setup. also, windows 8.1 blocks your installer, stating that it is from an unknown publisher or something like that. not sure if this is a problem, though. I bypassed it by forcing windows to ignore the signature. (yeah, I spent a few years in Clemson and even a few months in NC triangle area which I liked a lot. I get to keep this email even after graduation.) On Wed, Mar 23, 2016 at 6:48 PM, Steve Hall <dig...@da...> wrote: > On Wed, Mar 23, 2016 at 6:55 PM, Meng Zhu <meng@g.clemson.edu> wrote: > > > > doesn't anyone know a cream vim that supports python/python3/ruby > > and does run without errors? > > Today might be your lucky day... try 7.4.1641 from here: > https://sourceforge.net/projects/cream/files/Vim/ > > Ruby has been broken in Vim builds for MONTHS. But for the first time > ever, Ruby 2.2 built for me today. > > Can you test this? See any errors? I'm curious if 2.2 works for > everyone, or are there some legacy users out there who need 1.9? > > (Clemson, eh? We're practically neighbors, I'm just 4-5 hours up I-85 > from there in Raleigh-Durham.) > > -- > Steve Hall [ digitect dancingpaper com ] > Cream for Vim http://cream.SourceForge.net > <http://cream.sourceforge.net/> > SteveHallArchitecture http://SteveHallArchitecture.com > <http://stevehallarchitecture.com/> > > |
From: Steve H. <dig...@da...> - 2016-03-24 01:48:56
|
On Wed, Mar 23, 2016 at 6:55 PM, Meng Zhu <meng@g.clemson.edu> wrote: > > doesn't anyone know a cream vim that supports python/python3/ruby > and does run without errors? Today might be your lucky day... try 7.4.1641 from here: https://sourceforge.net/projects/cream/files/Vim/ Ruby has been broken in Vim builds for MONTHS. But for the first time ever, Ruby 2.2 built for me today. Can you test this? See any errors? I'm curious if 2.2 works for everyone, or are there some legacy users out there who need 1.9? (Clemson, eh? We're practically neighbors, I'm just 4-5 hours up I-85 from there in Raleigh-Durham.) -- Steve Hall [ digitect dancingpaper com ] Cream for Vim http://cream.SourceForge.net <http://cream.sourceforge.net/> SteveHallArchitecture http://SteveHallArchitecture.com <http://stevehallarchitecture.com/> |
From: Meng Z. <meng@g.clemson.edu> - 2016-03-23 23:19:28
|
I am on Windows 8.1 and I use cream vim instead the one from here ( http://www.vim.org/download.php) because I find cream vim has support to python, python3 and ruby, which are necessary for some plugins that I use. unfortunately, when using ruby,I ran into errors: E448: ... could not load rb_float_new_in_heap E266: sorry, this command is disable... I can see my cream vim was compiled with ruby support from :version as it lists +ruby/dyn and -DFEAT_RUBY -I /cygdrive/c/Ruby193/lib/ruby/1.9.1/i386-mingw32 -I /cygdrive/c/Ruby193/include/ruby-1.9.1 -I /cygdrive/c/Ruby193/include/ruby-1.9.1/i386-mingw32 -DDYNAMIC_RUBY -DDYNAMIC_RUBY_DLL="msvcrt-ruby191.dll" -DDYNAMIC_RUBY_VER=*191 * I googled a bit about the errors and found this page ( https://groups.google.com/forum/#!topic/vim_dev/N7oUbqFmOvw) which suggests the correct RUBY_VER macro should have been 19 instead of 191. I also took a look at vim source if_ruby.c and indeed its logic branches on RUBY_VER 19. # if *DYNAMIC_RUBY_VER* <= *19* {"rb_float_new", (RUBY_PROC*)&dll_rb_float_new}, # else {"rb_float_new_in_heap", (RUBY_PROC*)&dll_rb_float_new}, # endif from the logic, it looks like rb_float_new should be used for RUBY_VER<=19, and I can find that function in my msvcrt-ruby191.dll shipped with ruby-1.9.1-p429-i386-mswin32.zip, but not rb_float_new_in_heap, which explained the error. my question is, doesn't anyone know a cream vim that supports python/python3/ruby and does run without errors? Thanks. I tried to grab the latest from http://cream.sourceforge.net/, which looks like support ruby and has RUBY_VER set to 18, but it doesn't have support for python3 for some reason and there is also no vim.exe after installation (i.e., only gvim.exe) which is a big no no to me. Thanks for any comments or pointers. Meng |
From: Steve H. <dig...@da...> - 2015-12-23 13:27:43
|
On Tue, Dec 22, 2015 at 4:51 PM, John <gr...@gm...> wrote: > > Hello, this may be a very basic question but I have not found a > solution as of yet. All I want is that when I press the End key it > will go to the actual end of the line, not having the cursor before > a semicolon or curly brace. I know I can press Alt+End to do this > but it would be more convenient if I could have the End button do > it. Thank you. This has bothered me since Vim adjusted line end positioning several years ago. But I think I just figured out a simple solution, could you test it for me? In cream-lib.vim, replace the Cream_map_end() definition with the following: _____________________________________________________________________ function! Cream_map_end() " get current pos let oldcol = virtcol('.') " go to last screen column normal g$ " Hack: fix that <C-b> doesn't allow ending up after last char " with wrap off (2004-04-23) if &wrap == 0 " if line is shorter than screen if virtcol('$') < Cream_linewidth() " fix position normal $ " if we were already at screen line end elseif oldcol >= virtcol('.') " move farther normal $ else " nothing, first g$ did what we wanted endif else " if already at screen end, go to line end if oldcol < virtcol('.') if col(".") == col("$") - 1 normal $ endif elseif oldcol == virtcol('.') normal $ else endif endif endfunction _____________________________________________________________________ This works for me, please report back how this works for you. -- Steve Hall [ digitect dancingpaper com ] Cream for Vim http://cream.SourceForge.net http://SteveHallArchitecture.com |
From: John <gr...@gm...> - 2015-12-22 21:51:46
|
Hello, this may be a very basic question but I have not found a solution as of yet. All I want is that when I press the End key it will go to the actual end of the line, not having the cursor before a semicolon or curly brace. I know I can press Alt+End to do this but it would be more convenient if I could have the End button do it. Thank you. |
From: Erik Z. <eri...@gm...> - 2015-08-13 23:06:08
|
Thanks Steve, I'm glad that it will be easy to copy in a new vimrc version and switch back and forth between the two modes. It didn't work when I tried it. However I had previously mucked around with a couple of things on my system, so I will try it again using a fresh install of MacVim and a fresh install of Cream soon, when I am able. Thanks, Erik On Tue, Aug 11, 2015 at 9:36 AM, Steve Hall <dig...@da...> wrote: > On Tue, Aug 11, 2015 at 7:15 AM, Erik Zoltan <eri...@gm...> > wrote: > > To summarize, I haven't been able to get it to run. Therefore I am > > suggesting two solutions below. > > > > The Mac port of gvim was withdrawn at some point in the past. MacVim > > is typically used. MacVim is a fully functional version of gvim. It > > has the added benefit of being compatible with the Mac clipboard, > > fully supporting the Mac App functionality, and looking truly lovely > > on a Retina display. > > > > Unfortunately MacVim does not accept the normal gvim startup > > arguments. It is normally launched as a graphical app within Mac OS > > X. You can pass startup arguments to it with the mac-unix open > > command, however MacVim is either not expecting them, or is missing > > some extra step to support them. > > > > ***This prevents Cream from running on a Mac.*** > > > > Two separate but complementary things can be done to address this > > issue. > > > > 1. (Out of scope for the Cream project — in scope for the MacVim > > project). Someone can fix MacVim to accept command line > > arguments, and hopefully make a “gvim” script alias that will > > pass that information along to MacVim. > > > > 2. (In scope for Cream) Someone can produce a patch to the vim > > scripts that causes Cream to be used without any gvim command > > line arguments. This would consist of hard-coding the information > > that the cream startup command normally passes along to gvim. It > > would prevent gvim from being used without Cream, so it should be > > done in a way that makes it easy for someone to go in and disable > > it, by commenting out a single line for example. Especially if > > MacVim has further incompatibilities. > > > > If someone knows of a way to patch the vim scripts as mentioned in > > item 2 above, then I would be excited to try it out. Has anyone done > > that before? > > Thanks for this report. > > Cream uses only three command line arguments: > > 1. -u to force the vimrc name > 2. -U to prevent a gvimrc (NONE) > 3. --servername to force the server name to "CREAM" > > These would not be necessary with the following tiny adjustments: > > 1. The creamrc is renamed vimrc and located at the default Vim > location so that gVim automatically finds and uses it > 2. No gvimrc is installed > 3. The CREAM server name is changed back to GVIM in cream-server.vim > (four spots, beginning about line 203). > > With just these changes, MacVim should function as Cream. Can you > test? > > -- > Steve Hall [ digitect dancingpaper com ] > Cream for Vim http://cream.SourceForge.net > SteveHallArchitecture http://SteveHallArchitecture.com > > |
From: Steve H. <dig...@da...> - 2015-08-11 13:48:55
|
On Tue, Aug 11, 2015 at 7:15 AM, Erik Zoltan <eri...@gm...> wrote: > To summarize, I haven't been able to get it to run. Therefore I am > suggesting two solutions below. > > The Mac port of gvim was withdrawn at some point in the past. MacVim > is typically used. MacVim is a fully functional version of gvim. It > has the added benefit of being compatible with the Mac clipboard, > fully supporting the Mac App functionality, and looking truly lovely > on a Retina display. > > Unfortunately MacVim does not accept the normal gvim startup > arguments. It is normally launched as a graphical app within Mac OS > X. You can pass startup arguments to it with the mac-unix open > command, however MacVim is either not expecting them, or is missing > some extra step to support them. > > ***This prevents Cream from running on a Mac.*** > > Two separate but complementary things can be done to address this > issue. > > 1. (Out of scope for the Cream project — in scope for the MacVim > project). Someone can fix MacVim to accept command line > arguments, and hopefully make a “gvim” script alias that will > pass that information along to MacVim. > > 2. (In scope for Cream) Someone can produce a patch to the vim > scripts that causes Cream to be used without any gvim command > line arguments. This would consist of hard-coding the information > that the cream startup command normally passes along to gvim. It > would prevent gvim from being used without Cream, so it should be > done in a way that makes it easy for someone to go in and disable > it, by commenting out a single line for example. Especially if > MacVim has further incompatibilities. > > If someone knows of a way to patch the vim scripts as mentioned in > item 2 above, then I would be excited to try it out. Has anyone done > that before? Thanks for this report. Cream uses only three command line arguments: 1. -u to force the vimrc name 2. -U to prevent a gvimrc (NONE) 3. --servername to force the server name to "CREAM" These would not be necessary with the following tiny adjustments: 1. The creamrc is renamed vimrc and located at the default Vim location so that gVim automatically finds and uses it 2. No gvimrc is installed 3. The CREAM server name is changed back to GVIM in cream-server.vim (four spots, beginning about line 203). With just these changes, MacVim should function as Cream. Can you test? -- Steve Hall [ digitect dancingpaper com ] Cream for Vim http://cream.SourceForge.net SteveHallArchitecture http://SteveHallArchitecture.com |
From: Erik Z. <eri...@gm...> - 2015-08-11 11:16:01
|
To summarize, I haven't been able to get it to run. Therefore I am suggesting two solutions below. The Mac port of gvim was withdrawn at some point in the past. MacVim is typically used. MacVim is a fully functional version of gvim. It has the added benefit of being compatible with the Mac clipboard, fully supporting the Mac App functionality, and looking truly lovely on a Retina display. Unfortunately MacVim does not accept the normal gvim startup arguments. It is normally launched as a graphical app within Mac OS X. You can pass startup arguments to it with the mac-unix open command, however MacVim is either not expecting them, or is missing some extra step to support them. ***This prevents Cream from running on a Mac.*** Two separate but complementary things can be done to address this issue. 1. (Out of scope for the Cream project — in scope for the MacVim project). Someone can fix MacVim to accept command line arguments, and hopefully make a “gvim” script alias that will pass that information along to MacVim. 2. (In scope for Cream) Someone can produce a patch to the vim scripts that causes Cream to be used without any gvim command line arguments. This would consist of hard-coding the information that the cream startup command normally passes along to gvim. It would prevent gvim from being used without Cream, so it should be done in a way that makes it easy for someone to go in and disable it, by commenting out a single line for example. Especially if MacVim has further incompatibilities. If someone knows of a way to patch the vim scripts as mentioned in item 2 above, then I would be excited to try it out. Has anyone done that before? Thanks, Erik |
From: Erik Z. <eri...@gm...> - 2015-06-27 02:09:34
|
MacVim can be installed via macports. It is like gvim, except it more Mac-like. It integrates better with the Mac clipboard for example, and uses Mac-style keyboard equivalents. And looks great on a retina display. At the same time, my .vimrc and the scripts in my .vim directory work just fine. $sudo port install MacVim You can't run gvim. MacVim can be run from the command line as follows: /Applications/MacVim.app/Contents/MacOS/MacVim However it doesn't seem to support the command line arguments that gvim supports. I don't think they handle the same command line arguments. So when I run it from my cream.sh script it comes up like normal vim. I will keep researching. Thanks, Erik On Thu, Jun 25, 2015 at 10:53 PM, Steve Hall <dig...@da...> wrote: > On Thu, Jun 25, 2015 at 11:59 AM, Erik Zoltan <eri...@gm...> > wrote: > > > > Does anyone have experience getting Cream to work with MacVim, or > > should I be trying to install gVim instead? > > Is the MacVim stable and have all the features of the other versions? > > > I'd love to create a document describing the easiest way to get > > Cream running on a Mac and submit it for inclusion in the project. > > I would equally love to be able to add that to Cream. > > > I'm working with Cream as my programmer's editor. I have it on Linux > > and have used it on Windows. I do most of my work on a MacBook Pro > > and would love to get Cream running on Mac. I use MacVim which works > > great but I would rather use Cream with expert mode. I have syntax > > highlighting language bindings for vim that I can't get in other > > editors, so I'm already committed to something vim-ish. > > I've never had a user willing to work it all out but would welcome the > opportunity. I'm don't know any of the particular Apple environment > requirements. Knowing Vim, there are probably just a few tweaks > needed. > > If you're interested, start with the creamrc. All the paths will need > to be verified before anything else will work. That's probably it > other other than issues with GUI pieces like dialogs, menus, window > size, etc. > |
From: Steve H. <dig...@da...> - 2015-06-26 03:11:03
|
On Thu, Jun 25, 2015 at 11:59 AM, Erik Zoltan <eri...@gm...> wrote: > > Does anyone have experience getting Cream to work with MacVim, or > should I be trying to install gVim instead? Is the MacVim stable and have all the features of the other versions? > I'd love to create a document describing the easiest way to get > Cream running on a Mac and submit it for inclusion in the project. I would equally love to be able to add that to Cream. > I'm working with Cream as my programmer's editor. I have it on Linux > and have used it on Windows. I do most of my work on a MacBook Pro > and would love to get Cream running on Mac. I use MacVim which works > great but I would rather use Cream with expert mode. I have syntax > highlighting language bindings for vim that I can't get in other > editors, so I'm already committed to something vim-ish. I've never had a user willing to work it all out but would welcome the opportunity. I'm don't know any of the particular Apple environment requirements. Knowing Vim, there are probably just a few tweaks needed. If you're interested, start with the creamrc. All the paths will need to be verified before anything else will work. That's probably it other other than issues with GUI pieces like dialogs, menus, window size, etc. |
From: Erik Z. <eri...@gm...> - 2015-06-25 15:59:30
|
Does anyone have experience getting Cream to work with MacVim, or should I be trying to install gVim instead? I'd love to create a document describing the easiest way to get Cream running on a Mac and submit it for inclusion in the project. I'm working with Cream as my programmer's editor. I have it on Linux and have used it on Windows. I do most of my work on a MacBook Pro and would love to get Cream running on Mac. I use MacVim which works great but I would rather use Cream with expert mode. I have syntax highlighting language bindings for vim that I can't get in other editors, so I'm already committed to something vim-ish. Thanks, Erik |
From: Adam L. <asl...@gm...> - 2014-05-27 12:49:55
|
On 05/26/2014 10:49 AM, Steve Hall wrote: > > My fix is similar, adding line 136 to the end of the words lowercased > series: > > let @x = substitute(@x, "'S", "'s", 'g') > Although the simplicity of that fix is great, I didn't do it that way because it doesn't handle quotes correctly. For example, it would un-capitalize the first word inside single quotes if it began with S: THE 'SECOND' TITLE --> The 'second' Title when what I want would be The 'Second' Title Therefore, my regex must find a "word" character before the quote/apostrophe, and also the S must be at the end of the word. I also assert that it must be a case-sensitive match, although that's probably unnecessary. On a side note...unless I'm missing something, the entire "optional lowercase" section is in the wrong place in the script. Of course since it's commented out it doesn't matter...until you try to use it. I think it should come before the "fix first word again" line; otherwise optionally lowercased words are not re-capitalized when they appear first or last in the selection. Maybe few people have used this functionality very much. My job of late has required processing a bunch of old data into HTML to make it available on our website. After the modifications mentioned above, your script has proven extremely helpful. Best regards Adam |
From: Steve H. <dig...@da...> - 2014-05-26 16:12:35
|
[cream-capitalization plugin http://www.vim.org/scripts/script.php?script_id=242] On Fri, May 23, 2014 at 4:24 PM, Adam Lehigh <asl...@gm...> wrote: > > The Problem: title case is not done the way I want when starting from > uppercase and having possessives. > > I would like to see the "S" after the apostrophe be lowercase also. Good catch, I can't believe that bug has been there 6 years! My fix is similar, adding line 136 to the end of the words lowercased series: let @x = substitute(@x, "'S", "'s", 'g') -- Steve Hall [ digitect dancingpaper com ] Cream for Vim http://cream.SourceForge.net <http://cream.sourceforge.net/> SteveHallArchitecture http://SteveHallArchitecture.com<http://stevehallarchitecture.com/> |
From: Adam L. <asl...@gm...> - 2014-05-23 20:24:32
|
After putting up with this for a while I got aggravated enough to do something about it.... The Problem: title case is not done the way I want when starting from uppercase and having possessives. start with this: VIM'S SETTINGS after selecting the line and hitting F5 I get: Vim'S Settings I would like to see the "S" after the apostrophe be lowercase also. My Solution: I have gotten it working to my satisfaction by adding this line to cream-capitalization.vim in the title case section after fixing the last word again: let @x = substitute(@x, "\\C\\w'\\zsS\\>", "s", "g") There may be a better way to do it, I haven't really thought through what might be expected behavior in all cases; but this works for me. More Explanation: I don't actually use Cream, but have found this particular plugin quite useful in my line of work. Installed version is 2.4 from GitHub. |
From: plmalternate p. <plm...@gm...> - 2014-02-09 10:37:13
|
Yes, indeed. I created the file with the one line and made a second copy for /root/.cream/. Works perfectly. Not sure how I missed that in the FAQ. Thank you much, sir. |
From: Steve H. <dig...@da...> - 2014-02-08 17:22:07
|
On Fri, Feb 7, 2014 at 8:20 PM, plmalternate plmalternate < plm...@gm...> wrote: > > I'm trying to disable swapfile creation. Gvim seems to honor > > set noswapfile > > in ~/.vimrc and /root/.vimrc, but Cream is ignoring it. > > I added > set noswapfile > at the end of: > /usr/share/vim/cream/cream-conf.vim This is sourced BEFORE Cream's intialization. > & > /usr/share/vim/cream/creamrc > and rebooted. > > That didn't work. > > Suggestions where I should look, please? TIA gentlesapients. Since Cream sets swapfile during startup, you want to put it in cream-user.vim which is triggered AFTER initialization: http://cream.sourceforge.net/faq.html#0201 Does that work? -- Steve Hall [ digitect dancingpaper com ] :: Cream for Vim http://cream.sourceforge.net |
From: plmalternate p. <plm...@gm...> - 2014-02-08 01:20:38
|
I'm trying to disable swapfile creation. Gvim seems to honor set noswapfile in ~/.vimrc and /root/.vimrc, but Cream is ignoring it. I added set noswapfile at the end of: /usr/share/vim/cream/cream-conf.vim & /usr/share/vim/cream/creamrc and rebooted. That didn't work. Suggestions where I should look, please? TIA gentlesapients. ------------ Additional explanation only for those tempted to reply "Don't DO that because . . .": With no disrespect intended, here's why I believe that would not be a useful response: 1-I'm the only user on my system. 2-I deal with backups of critical text files in my own way. I open all text files (in the broad sense, including xml, etc.) with a script that offers a choice of editors with or without backup creation, tests for needed permissions on the file and its parent directory and then opens with or without gksu as needed. If a backup is chosen, it is dated in the filename. So the system is uniform, no matter what editor I use, I DON'T NEED an additional safety net. The safety net I already have is better. 3-I've edited sudoers without visudo for years and I haven't had a disaster yet. Gimme a break. Thank you. |
From: Steve H. <dig...@da...> - 2014-01-03 04:20:37
|
On Thu, Jan 2, 2014 at 10:14 PM, umberto boccioni <ve...@gm...> wrote: > > I'm having an issue getting Vundle, the plug-in installer, running > normally with Cream (Win7x64, using the v7.3.107 binaries). The > issue amounts to having to run :BundleInstall (usually a one-time > command) each time I start Vim/Cream. I outlined the issue here > http://stackoverflow.com/questions/20666115/is-bundleinstall-for-vundle-required-every-time-vim-is-started/ > , and it was speculated that it was related to something Cream is > doing to the runtime path (since that's the only thing > :BundleInstall does if the requisite plugins have already been > downloaded/copied). I have the Vundle commands in my cream-user.vim > file, which, per documentation is "loaded at the end of startup. We > recommend that all customizations be placed here so they are able to > over-ride any Cream settings if desired." I'm not sure what > constitutes "end of startup," but I do note quite a few files are > listed after cream-user.vim in the scriptnames listing. > > Is the issue Cream-related? Having to type :BundleInstall each time > is a fairly trivial workaround, so I'm willing to live with it for > now. Is Vundle required each session or is it simply a script version updater to be run manually? Cream uses a series of autocmds (in cream-autocmd.vim) to manage global variables and corresponding buffer variables which control just about everything from menus, windows, tabs, buffers, syntax highlighting, etc. Depending on what you need Vundle to do, it's autocmds will need to be coordinated. I can give you some more tips if you need. If it is simply a path set, your &rtp setting looks okay to me. I recommend putting everything into functions so you have better control: function! MyVundle() " do Vundle stuff here endfunction " below will be called every time, comment and call it " from command line to control manually call MyVundle() " sets a keystroke to do this imap <silent> <F12> <C-l>:call MyVundle()<CR> Make sense? Where is AutoSaveToggle defined? This is not a standard Vim command, and doesn't appear to be defined by your customizations according to your E492 error. -- Steve Hall [ digitect dancingpaper com ] :: Cream for Vim http://cream.sourceforge.net |
From: umberto b. <ve...@gm...> - 2014-01-03 03:14:54
|
I'm having an issue getting Vundle, the plug-in installer, running normally with Cream (Win7x64, using the v7.3.107 binaries). The issue amounts to having to run :BundleInstall (usually a one-time command) each time I start Vim/Cream. I outlined the issue here http://stackoverflow.com/questions/20666115/is-bundleinstall-for-vundle-required-every-time-vim-is-started/, and it was speculated that it was related to something Cream is doing to the runtime path (since that's the only thing :BundleInstall does if the requisite plugins have already been downloaded/copied). I have the Vundle commands in my cream-user.vim file, which, per documentation is "loaded at the end of startup. We recommend that all customizations be placed here so they are able to over-ride any Cream settings if desired." I'm not sure what constitutes "end of startup," but I do note quite a few files are listed after cream-user.vim in the scriptnames listing. Is the issue Cream-related? Having to type :BundleInstall each time is a fairly trivial workaround, so I'm willing to live with it for now. -- ub |
From: Steve H. <dig...@da...> - 2013-12-18 14:16:06
|
On Wed, Dec 18, 2013 at 3:18 AM, Dmitry Frank <dim...@gm...> wrote: > > I just checked that there is Vim 7.4.110 built with +ruby > http://sourceforge.net/projects/cream/files/Vim/7.4.110/ I tried it, > and I see that :version returns +ruby/dyn , but has('ruby') still > returns 0. > > I tried :ruby puts 1 , it failed: it seems, it can't find ruby > installed on the machine. But, Vim 7.3 works just fine with ruby. > (ruby version is 1.9.3p392 ) > > What could be wrong? Good question, same problem for me. I don't understand the Vim internals, but it seems like some of the outlier build and dependency changes aren't yet up to date. (I'm counting my cross-platform build as one of them.) -- Steve Hall [ digitect dancingpaper com ] :: Cream for Vim http://cream.sourceforge.net :: SteveHallArchitecture http://stevehallarchitecture.com |
From: Dmitry F. <dim...@gm...> - 2013-12-18 08:18:43
|
Steve, hello again. I just checked that there is Vim 7.4.110 built with +ruby http://sourceforge.net/projects/cream/files/Vim/7.4.110/ I tried it, and I see that :version returns +ruby/dyn , but has('ruby') still returns 0. I tried :ruby puts 1 , it failed: it seems, it can't find ruby installed on the machine. But, Vim 7.3 works just fine with ruby. (ruby version is 1.9.3p392 ) What could be wrong? -- Dmitry 2013/10/28 Dmitry Frank <dim...@gm...> > Steve, thank you very much. > > I anyway need for ruby though, so, have to wait until Vim is able to build > with +ruby.. > > > 2013/10/27 Steve Hall <dig...@da...> > >> On Sun, Oct 27, 2013 at 2:03 AM, Dmitry Frank <dim...@gm...> >> wrote: >> > > > >> > > > Could you please build Vim 7.4 with +ruby and +python again? Or, >> > > > why have you decided to exclude these features? >> >> [...] >> >> For anyone following this thread, I have just posted a Windows >> installer updated to 7.4.52: >> >> http://sourceforge.net/projects/cream/files/Vim/ >> >> The release notes are there, but I'll point out Perl, Ruby, and TCL >> are all still broken in the Cygwin build process of a stand-alone >> (non-Cygwin dependent) gVim. >> >> Still no updates on the Cream side... yet. >> >> -- >> Steve Hall [ digitect dancingpaper com ] >> :: Cream for Vim [ http://cream.sourceforge.net ] >> > > |
From: Dmitry F. <dim...@gm...> - 2013-10-28 08:02:40
|
Steve, thank you very much. I anyway need for ruby though, so, have to wait until Vim is able to build with +ruby.. 2013/10/27 Steve Hall <dig...@da...> > On Sun, Oct 27, 2013 at 2:03 AM, Dmitry Frank <dim...@gm...> > wrote: > > > > > > > > Could you please build Vim 7.4 with +ruby and +python again? Or, > > > > why have you decided to exclude these features? > > [...] > > For anyone following this thread, I have just posted a Windows > installer updated to 7.4.52: > > http://sourceforge.net/projects/cream/files/Vim/ > > The release notes are there, but I'll point out Perl, Ruby, and TCL > are all still broken in the Cygwin build process of a stand-alone > (non-Cygwin dependent) gVim. > > Still no updates on the Cream side... yet. > > -- > Steve Hall [ digitect dancingpaper com ] > :: Cream for Vim [ http://cream.sourceforge.net ] > |