File Explorer will not work on Windows XP

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

_______________________________________________
cream-general mailing list
cream-general@...
https://lists.sourceforge.net/lists/listinfo/cream-general

Re: File Explorer will not work on Windows XP

This is a bug I was just debating with myself this morning. The old vim
plugin has been replaced with netrw, which leaves Cream in a bind. A
number of users have requested a project manager, and I've been debating
on implementing something that can do both files and projects. 

But nothing is set in stone, for big things I sometimes contemplate them
for months unless I get a lot of feedback here for a good solution.

With that, I'll open the floor--suggestions?

On Sat, 2007-09-01 at 11:27 -0400, Joe Hodsdon wrote:
> I recently installed Cream 0.39 with Vim 7.1 on Windows XP, and the
> 'Window' > 'Open File Explorer' command won't work. When I select it,
> a command prompt window flashes for a second (vimrun.exe is executing
> the command [C:\Windows\system32\cmd.exe /c cmd /c "D:\directory\of
> \current\file"]) and disappears, but no Explorer window is displayed.
> 
> Has anyone experienced this? Can anyone offer some suggestions? 
> 
> Thanks,
> Joe 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________ cream-general mailing list
cream-general@... https://lists.sourceforge.net/lists/listinfo/cream-general

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: Poor perfomance (was Re: setting default backup and swap dirs)

Remember this one, Steve?  Well, when we upgraded recently to 0.39, this 
broke again, so I had to reapply your fix.  It would be nice if this 
could be implemented as a "performance feature" as you suggested so I 
wouldn't have to carry the patch forward from version to version.

Thanks,
Ben

Steve Hall wrote:
> On Thu, 2005-09-08 at 08:38 -0300, BG - Ben Armstrong wrote:
>   
>> On Wed, 2005-09-07 at 17:25 -0400, Steve Hall wrote:
>>     
>>> Cream tries to display the read-only status of a file in two
>>> places: the statusline and the window title. If you test:
>>>
>>>   set statusline&
>>>   set titlestring&
>>>
>>> in your cream-user, you should see this problem go away.
>>>
>>> Does that work?
>>>       
>> That's it! Thanks. Looking forward to a proper fix so I can
>> deliver this to my users. Obviously not having the status line at
>> all is a Bad Thing. :)
>>     
>
> A good temporary solution would be:
>
> 1. Add a line at the top of cream-statusline function
>    Cream_statusline_filestate() to:
>
>      return ""
>
> 2. Replace the cream-settings function Cream_titletext() lines:
>
>      " modified
>      if getbufvar(mybufnr, "&modified") == 1
>         let mymod = "*"
>      else
>         let mymod = ""
>      endif
>
>    to
>
>      let mymod = ""
>
> I suppose we could make these automatic with some cream-conf var. But
> I've also been thinking about adding "performance settings" for large
> or high latency files. They could be meta controls for items like
> those above, as well as &lazyredraw, &swapfiles, &backup, :syntax and
> whatever else typically causes performance problems in select
> situations.
>
>
>   

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: Poor perfomance (was Re: setting default backup and swap dirs)

Ben, for now, you might try redefining these two functions in
$CREAM."cream-user.vim" or in the Cream_conf_override() of a
system-wide cream-conf:

  function! Cream_statusline_filestate()
    return ""
  endfunction

  function! Cream_titletext()
      ...
      let mymod = ""
      ...
  endfunction

Then they will overwrite the corresponding Cream functions until
somebody finds time to write a patch for this. :)

--
Steve Hall  [ digitect dancingpaper com ]
:: Cream... usability for Vim
::   http://cream.sourceforge.net

On Tue, 2007-09-04 at 11:01 -0300, Ben Armstrong wrote:
> Remember this one, Steve?  Well, when we upgraded recently to 0.39,
> this broke again, so I had to reapply your fix.  It would be nice if
> this could be implemented as a "performance feature" as you
> suggested so I wouldn't have to carry the patch forward from version
> to version.
>
> Thanks,
> Ben
>
> Steve Hall wrote:
> > On Thu, 2005-09-08 at 08:38 -0300, BG - Ben Armstrong wrote:
> >
> > > On Wed, 2005-09-07 at 17:25 -0400, Steve Hall wrote:
> > >
> > > > Cream tries to display the read-only status of a file in two
> > > > places: the statusline and the window title. If you test:
> > > >
> > > > set statusline&
> > > > set titlestring&
> > > >
> > > > in your cream-user, you should see this problem go away.
> > > >
> > > > Does that work?
> > > >
> > > That's it! Thanks. Looking forward to a proper fix so I can
> > > deliver this to my users. Obviously not having the status line
> > > at all is a Bad Thing. :)
> > >
> >
> > A good temporary solution would be:
> >
> > 1. Add a line at the top of cream-statusline function
> > Cream_statusline_filestate() to:
> >
> > return ""
> >
> > 2. Replace the cream-settings function Cream_titletext() lines:
> >
> > " modified
> > if getbufvar(mybufnr, "&modified") == 1
> > let mymod = "*"
> > else
> > let mymod = ""
> > endif
> >
> > to
> >
> > let mymod = ""
> >
> > I suppose we could make these automatic with some cream-conf var.
> > But I've also been thinking about adding "performance settings"
> > for large or high latency files. They could be meta controls for
> > items like those above, as well as &lazyredraw, &swapfiles,
> > &backup, :syntax and whatever else typically causes performance
> > problems in select situations.
> >
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

0.39 alternate spellings popup menu 'sticky'

Hi,

Peter spotted this one today:

1. position cursor on a word
2. alt-f7 to bring up alternate spellings popup menu (doesn't matter if 
you select one or not)
3. select some text anywhere in the document
4. right-click
- expected result: popup menu including undo, cut, copy, etc. appears
- actual result: popup menu containing alternate spellings appears again!

Workaround:

1. unselect text region
2. right-click
- popup menu including undo, paste, select all, etc. appears
3. select some text in the document again
4. right-click
- popup menu including undo, cut, copy, etc. appears

Ben

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: Problem with Cream/Vim installer

On Thu, 2007-09-06 at 19:26 +0900, Albert Novick wrote:
>
> Thanks very much for your quick response and helpful suggestion. I
> removed the libintl.dll file from the previous Vim installation
> folder.

Thanks for that info, this could be a clue. It appears our installer
does not install one of these. I'm not on a Windows machine at the
moment to check our build process, but will check into whether it
should.

> Curiously, even after rebooting, the cream-0-39-gvim-7-1-2.exe file
> still proceeded in German (or something), but Vim had changed from
> Japanese to English. So I ran the cream/vim installer anyway, and it
> installed in English.

So the initial install is still wrong, but a re-install gets it right?

--

-- 
Steve Hall  [ digitect dancingpaper com ]
:: Cream... usability for Vim
::   http://cream.sourceforge.net

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: Problem with Cream/Vim installer

From: Albert Novick, Sun, September 09, 2007 11:38 pm
>
> > So the initial install is still wrong, but a re-install gets it
> > right?
>
> I only installed once. I started the installer a few times, but
> always aborted it before the install could begin because it was in
> the wrong language. The first time I went through with the install,
> I ended up with a normal Cream/Vim installation, all in English.
> Before doing that, I had removed the libintl.dll file from the Vim
> 7.0 folder that I already had installed. The immediate effect of
> doing that was that the Vim displays that had been in Japanese (as
> mentioned, my system is Japanese Windows XP) now were in English.
> The new Vim 7.1.2 and Cream installation were also in English.
>
> Just to see what would happen, I replaced the libintl.dll file in
> the new Vim installation and rebooted, but now there were no
> displays in Japanese, except for the ones that Windows generates.

I'm not sure how the libintl.dll works (:help win32-gettext). This is
something that the native Vim installers can install or that a user
can install from a separate distribution. But Cream does not include
it since our langauge support is basically non-existant.

> Finally, I tried starting cream-0-39-gvim-7-1-2.exe again. As ever,
> it said "Velcommen til setup-guiden....!" (Maybe that's Dutch and
> not German, but it isn't English or Japanese.)

The installer is completely separate software from Cream/Vim. Why
Vim's libintl.dll would affect it is beyond me, although the Nullsoft
Installer code may be checking loaded libraries.

> I often experience troubles with websites that I reach by following
> links in English that automatically redirect me to Japanese pages
> because the site can tell that my system is Japanese. I would rather
> be given the option to choose the language I want. Maybe it would be
> good if your installer gave a language setting option.

I'll have to research this, NSIS has had issues with languages for
quite some time. What Cream does now is only permit the ASCII ones,
but it has been a while since I've researched fixes for this.

> I hope this is helpful, and I'm hoping I will eventually be able to
> use Cream and/or Vim to edit html files.

Let's keep working on this, I'd like for language support to at least
be predictable, even if it means the less-than-ideal English-only.

--

-- 
Steve Hall  [ digitect dancingpaper com ]
:: Cream... usability for Vim
::   http://cream.sourceforge.net

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Switch to new document tab

I'm trying Cream 0.39 on Windows XP SP2.  I have Tabbed Documents and Single 
Session Mode preferences enabled.  When using the Explorer 'Edit with 
Cream/&Vim' context menu, it opens the document in a new tab but does not 
switch to that tab.  How can I make it do that?  Thanks.

--

-- 
---------------------
Kyle Alons
http://www.kinook.com

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: Switch to new document tab

From: "Kyle Alons", Tue, September 11, 2007 9:39 am
> 
> I'm trying Cream 0.39 on Windows XP SP2. I have Tabbed Documents and
> Single Session Mode preferences enabled. When using the Explorer
> 'Edit with Cream/&Vim' context menu, it opens the document in a new
> tab but does not switch to that tab. How can I make it do that?
> Thanks.

Hmm, I don't see this, for me it switches to the correct tab. Did you
install with the default Cream installer? I'm wondering if there isn't
something in the registry setting for this menu item that is wrong,
the key:

HKEY_CLASSES_ROOT\*\Shell\Cream\Command

should have value [all on one line]:

"C:\Program Files\vim\vim71\gvim.exe" "-u" "C:\Program Files\vim\vim71\cream\creamrc" "-U"
"NONE" "--servername" "CREAM" "%1"

We've tweaked the library that handles this recently (although not for
this particular bug), you might try downloaded the latest version:

http://cream.cvs.sourceforge.net/cream/cream/cream-lib-win-tab-buf.vim?view=log

and copy it over your existing file. 

Does any of this help?

--

-- 
Steve Hall  [ digitect dancingpaper com ]
:: Cream... usability for Vim
::   http://cream.sourceforge.net

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: Switch to new document tab

"Steve Hall" <digitect@...> wrote in
message
news:20070911090343.2feb504d8ff40b56ee3289380ad93abe.f8ac27259b.wbe@...
> Hmm, I don't see this, for me it switches to the correct tab. Did you
> install with the default Cream installer?

Yes.

> I'm wondering if there isn't
> something in the registry setting for this menu item that is wrong,
> the key:
>
> HKEY_CLASSES_ROOT\*\Shell\Cream\Command
>
> should have value [all on one line]:
>
> "C:\Program Files\vim\vim71\gvim.exe" "-u" "C:\Program
> Files\vim\vim71\cream\creamrc" "-U" "NONE" "--servername" "CREAM" "%1"
>

That matches what I have (other than a slightly different path that I
installed to).

> We've tweaked the library that handles this recently (although not for
> this particular bug), you might try downloaded the latest version:
>
> http://cream.cvs.sourceforge.net/cream/cream/cream-lib-win-tab-buf.vim?view=log
>
> and copy it over your existing file.
>

That didn't help either.

If I close all documents in Cream, then open one via the Explorer context
menu, it opens in the first tab.  If I then open another one via the context
menu, it adds a new (last) tab for that document, and also opens another
recently opened file as the first tab and activates the first tab.

It works properly on a Windows 2000 virtual machine, so it be something 
funky about my PC.  Oh well. 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/