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

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.

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.

On Thu, Jan 2, 2014 at 10:14 PM, umberto boccioni <vexware@...> 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

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

On Wed, Dec 18, 2013 at 3:18 AM, Dmitry Frank <dimon.frank@...>
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

On Sun, Oct 27, 2013 at 2:03 AM, Dmitry Frank <dimon.frank@...> 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 ]

I'm using Python2.
I see that Vim binary has +python3/dyn, but -python and -ruby.
Please note that another Vim 7.4 binary is built successfully with +python
and +ruby : http://tuxproject.de.nyud.net/projects/vim/<http://goo.gl/BzdkjM>(current
version is 7.4.51 there)
2013/10/27 Steve Hall <digitect@...>
> On Sat, Oct 26, 2013 at 2:52 PM, Dmitry Frank <dimon.frank@...>
> wrote:
> >
> > I just have noticed that Vim 7.4.x built for Windows are built with
> > -ruby and -python . This is pretty disappointed for me, I have to
> > switch back to 7.3.x, since it is built with +ruby and +python.
> >
> > Could you please build Vim 7.4 with +ruby and +python again? Or, why
> > have you decided to exclude these features?
>
> What version of Python are you trying to use? I'm working today on
> getting both 2 and 3 included instead of just the first. We'll see.
>
> I'm disappointed about the Ruby, too, but Vim's build system has been
> long broken with these features. I think there was a recent patch, so
> maybe it is finally fixed. I'll include features as soon as Vim's
> build works with them.
>
> --
> Steve Hall [ digitect dancingpaper com ]
> :: Cream for Vim http://cream.sourceforge.net
>

On Sat, Oct 26, 2013 at 2:52 PM, Dmitry Frank <dimon.frank@...> wrote:
>
> I just have noticed that Vim 7.4.x built for Windows are built with
> -ruby and -python . This is pretty disappointed for me, I have to
> switch back to 7.3.x, since it is built with +ruby and +python.
>
> Could you please build Vim 7.4 with +ruby and +python again? Or, why
> have you decided to exclude these features?
What version of Python are you trying to use? I'm working today on
getting both 2 and 3 included instead of just the first. We'll see.
I'm disappointed about the Ruby, too, but Vim's build system has been
long broken with these features. I think there was a recent patch, so
maybe it is finally fixed. I'll include features as soon as Vim's
build works with them.
--
Steve Hall [ digitect dancingpaper com ]
:: Cream for Vim http://cream.sourceforge.net

Hello.
I just have noticed that Vim 7.4.x built for Windows are built with -ruby
and -python . This is pretty disappointed for me, I have to switch back to
7.3.x, since it is built with +ruby and +python.
Could you please build Vim 7.4 with +ruby and +python again? Or, why have
you decided to exclude these features?
Thanks.
--
Dmitry

On Mon, Sep 16, 2013 at 5:38 AM, Steve Hall <digitect@...>wrote:
> The intended behavior should be the word behind/preceeding. With Ctrl,
> the Backspace key should simply take a bigger gulp. I'll look into
> this.
>
One further bug report detail: it works correctly (deletes preceeding word)
only if the cursor is at the end of the line. If any characters follow the
cursor (white space included) it behaves incorrectly.
>
> I'm pleased to say that over the last few days I've gotten back into
> some new programming for Cream for the first time in years. I'm
> getting a new build system up and running and hope to release new
> Window Vim binaries and a new Cream version soon!
>
Thanks for the good work. Looking forward to it. Truly vim is a too
stringent for me to use without cream to soften it up.
--
ub

The intended behavior should be the word behind/preceeding. With Ctrl,
the Backspace key should simply take a bigger gulp. I'll look into
this.
I'm pleased to say that over the last few days I've gotten back into
some new programming for Cream for the first time in years. I'm
getting a new build system up and running and hope to release new
Window Vim binaries and a new Cream version soon!
--
Steve Hall [ digitect dancingpaper com ]

Hi, Umberto,
umberto boccioni wrote:
> What is the intended behavior of Ctrl+Backspace in cream? The keyboard
> shortcut page says the following:
>
> Ctrl+Backspace Delete word behind cursor
>
> ...but I find it deletes the following word.
"the word following the cursor" is exactly what I expect when reading "word
behind the cursor".
Just my thoughts,
Susan

What is the intended behavior of Ctrl+Backspace in cream? The keyboard
shortcut page says the following:
Ctrl+Backspace Delete word behind cursor
...but I find it deletes the following word. Is this the intended behavior
but with inaccurate documentation, or am I simply misunderstanding the
description? Shift+Backspace is also described as having the same
function, but has the same behavior.
I've come to use Ctrl+backspace all the time, so much so I don't even
realize I'm using it, so it's tough to give up. Incidentally, I note
there's no Ctrl+Delete, which would be the natural converse of
Ctrl+backspace (and perilously close to ctrl+alt+del, though MS Word gets
away with it)
Apologies for the basic-ness of the question, but every couple years i dip
back into vi and variants to try them out, but forget everything i learned
in the interim.
--
ub

On Wed, Sep 4, 2013 at 6:14 PM, Steve Hall <steve@...> wrote:
> A patch would be accepted. It has been years since anyone on the Mac
> platform expressed an interest in Cream, I'd be glad for some testing
> and feedback.
>
​Great. My vimscript isn't very deep, I've only ever made some syntax
highlighting rules and setup some functions and status bars.​
Any ideas on how to get the value of rformat?
I'm still another month out in getting some business issues sorted so
> I can build binaries and get back to patching Cream again. Please
> pardon the mess...
>
​As for mac binaries, much like MacVim, I bet that the overlap between OS X
users who want Cream and who are already running the open source code
porting system brew is close to %100. It may be easier to get it accepted
as a brew package and tell users to use brew rather than dive into the
whole mac native *.app packaging or native installer framework. Especially
because brew has some mechanisms to overriding Apple's local vim, which is
fine release, but slightly behind, especially wrt ruby. If you were to use
the mac native packaging you'd have to deal with overriding issues yourself.
And as I <3 brew, I might even be interested in doing this.
Or I could port Cream to iOS and put it in the app store. (Yes this is a
joke, given that most non BSD open source licenses conflict with the App
Store TOS. )
Indy
--
Indy M. Siverd
msiverd@...

On Wed, Sep 4, 2013 at 6:38 PM, Indy Siverd <msiverd@...> wrote:
>
> Trying to get Cream working with MacVim (one of two mac vim porting
> projects, this is the one that is still maintained).
[...]
> Also, if this is simple enough, I'll happily submit a diff with converted
> icons and the three lines of code I suspect are needed to increase your
> support of an "unsupported" MacVimCream.
A patch would be accepted. It has been years since anyone on the Mac
platform expressed an interest in Cream, I'd be glad for some testing
and feedback.
I'm still another month out in getting some business issues sorted so
I can build binaries and get back to patching Cream again. Please
pardon the mess...
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim (http://cream.sf.net)

Hey folks,
Trying to get Cream working with MacVim (one of two mac vim porting
projects, this is the one that is still maintained).
I've been a vi user for 20 years, and have done a fair amount of gvim on
linux, but I'm trying to move my devel enviroment to OS X.
I'm installing MacVim using brew, which puts the $VIMRUNTIME here:
/usr/local/Cellar/macvim/7.3-66/MacVim.app/Contents/Resources/vim/runtime
Which I had to force into $VRT in the INSTALL.sh script and it put things
in the "right" place. It's working and cream comes up from the command
line and has all the nice menu options and numbered buffers and colors.
My next problem is that MacVim doesn't like *.xpm icons in the toolbar and
would prefer *.png or *.tiff. Converting them is easy enough, but then I
need to tell cream to use them instead.
I found the following line in cream-cream-release.vim starting at line 174:
execute ':' . mysilent . '!' . copycmd . ' ' . quote . cream_cvs .
slash . 'addons' . slash . '*.vim' . quote . ' ' . quote . releasedir
. slash . 'addons' . quote
if rformat == "windows"
let bitmap = '*.bmp'
elseif rformat == "unix"
let bitmap = '*.xpm'
else
let bitmap = '*.*'
endif
Inside cream I've run ":let" to look at the variables, but I don't see a
value for "rformat" and I can't seem to get that "execute" to evaluate in
ex mode, but I suspect this is because we're in level of vimscript here
that is beyond my current skill. How can I find out the value of rformat
on my system? Then I'm going to add let bitmap = '*.png' and see if
everything is magically okay.
Huh, I supposed I could try doing that in my own .creamrc, but that's not
really the "right" way to solve this problem.
​Also, if this is simple enough, I'll happily submit a diff with converted
icons and the three lines of code I suspect are needed to increase your
support of an "unsupported" MacVimCream.​
​Indy​
--
Indy M. Siverd
msiverd@...

Hello,
apparently this same problem occurred previously (mail to this list by
BPJ on 2011-5-17 and answer by Steve Hall), but the solution offered
there does not work for me.
The problem is: I installed a syntax highlighting file to
~/.vim/syntax and a filetype detect file to ~/.vim/ftdetect. When I
open a file that fits the pattern, I get an error "E218: autocommand
nesting too deep".
The filetype detect command is "au BufNewFile,BufRead
*.markdown,*.md,*.mkd,*.pd,*.pdc,*.pdk,*.pandoc,*.text set
filetype=pandoc". As suggested by Steve, I tried inserting "nested"
before "set", but the problem remains.
The error does not occur with gvim or vim, and filetype autodetection works.
Anything I can do to get rid of this?
Thanks a lot,
Carsten

Hello,
Background: I was using Vim on Windows for some time now and wanted to
install the lua_omni plugin (so that I'd have lua syntax folding working).
After I've copied the files of the plugin to vim's directory and ran gVim,
gVim told me that it:
E370: Could not load library lua51.dll
I've searched for lua51.dll on Google and downloaded ~4KB file from
dllfiles.com. I've copied that file to %ProgramFiles%\vim\vim73 and
%windir%\system32. Vim was still complaining for the *.dll file. I've
tracked that the file that Vim was actually searching for was:
lua5.1.dll , and not:
lua51.dll (like the error message says)
After downloading lua5.1.dll - this time, not from dllfiles.com, but from
Lua's language website - copying the file to %programFiles%\Vim\vim73\
everything worked.
Please fix the filename in the error message / provide list of dirs for
which vim searches for the dll file in the error message if possible.
I'm using Vim 7.3.829.
Cheers.