Re: [cream] Menu bar disappeared

[William G. <gil...@gm...>]

Hmmm....I'm not sure. I've tried renaming all of the config files,
.cream, .vim, vimrc, and doing a complete removal of all vim and cream
packages. Then reinstalling all of them and I am still not getting a
menu bar on either cream or gvim. Also the permissions for .cream,
.vim, and vimrc all check out.

I don't believe that ubuntu would have updated the permissions. I am
skeptical that that would be the case as I had the menu bar, then
cream got a strange error loading multiple files, I closed it, then
reopened cream, and from then on out, I have no menu bar in gvim or
cream.

Do you have any other steps you would recommend. Maybe at this point
configurations or folders to check permissions on or purge, in order
to get a menu bar back?

Thanks in advance,
Bryan

On Tue, Oct 13, 2009 at 9:16 PM, Steve Hall <dig...@da...> wrote:
>
> I wonder if this could be some sort of a permissions problem. Does your
> username own and have read-write permissions to the Cream files? Note in
> the Vim help at :help 'secure that Vim will not allow autocmds on files
> not owned by the user, did Ubuntu change any of the Vim defaults that
> you know?
>
>
> On Tue, 2009-10-13 at 13:37 -0400, William Gilbert wrote:
>> Thanks for your reply, I am still unable to get the menu bar to show
>> up in either Cream or Gvim using ':set guioptions+=m'. I did find
>> however if I open either using sudo, that the menus appear correctly.
>> Anybody got any ideas?
>>
>> Thanks in advance,
>> Bryan
>>
>> On Tue, Oct 13, 2009 at 10:05 AM, Steve Hall <dig...@da...> wrote:
>> >
>> > Whoops, sorry that should have been:
>> >
>> >  :set guioptions+=m
>> >
>> > I don't find the Nautilus context menu very robust, it is apparently
>> > sending the entire string of files to what Vim understands to be a
>> > single argument. Not sure how to fix this, we were able to fix this
>> > via extra quoting in Windows Explorer.
>> >
>> > Steve
>> >
>> >
>> > From: William Gilbert, Tue, October 13, 2009 9:37 am
>> >>
>> >> Thanks for your reply!
>> >>
>> >> I tried running the ':guioptions+=m' in command mode, but I keep
>> >> getting 'E492: Not an editor command'. Please let me know if I'm
>> >> doing something wrong here.
>> >>
>> >> I opened the group of files, by selecting all of them in nautilus
>> >> and using the 'open with' option in the command menu. Do you think
>> >> maybe since cream didn't finish initializing properly and didn't
>> >> turn the menu back on, when I closed it, that wrote the setting back
>> >> out somewhere?.....Ok, I just checked gvim, and I'm seeing the same
>> >> thing there, I'll check out my vimrc file when I get a chance.
>> >>
>> >> Thanks again!
>> >> Bryan
>> >>
>> >> On Tue, Oct 13, 2009 at 7:36 AM, Steve Hall wrote:
>> >> > From: William Gilbert, Mon, October 12, 2009 10:10 pm
>> >> > >
>> >> > > I'm currently using ubuntu, and have been using cream for a few
>> >> > > weeks. Today, I tried to open a group of seven files and
>> >> > > received some odd errors, resulting in only three of the files
>> >> > > being opened and some odd behavior (open, format, and some other
>> >> > > functions weren't working). So, I closed the editor and reopened
>> >> > > it to find that there was no menu bar (file, edit, view, etc.).
>> >> > > I tried removing the package, renaming the .cream folder, but I
>> >> > > was unable to get the menu bar back. Anyone have any
>> >> > > suggestions?
>> >> >
>> >> > At the commandline [Ctrl+L, :]
>> >> >
>> >> > :guioptions+=m
>> >> >
>> >> > How are you opening a group of files? Cream initializes with the
>> >> > menu off to improve startup speed, but then turns it back on via
>> >> > autocmd. For some reason, the startup does not appear to be
>> >> > complete, it fails before the initialization autocmds finish.
>> >> >
>> >> > --
>> >> > Steve Hall  [ digitect dancingpaper com ]
>> >> > :: Cream... usability for Vim
>> >> > ::   http://cream.sourceforge.net
>> >> >
>> >
>> >
>> >
>>
>
>