Problems loading ecb

Re: Problems loading ecb

Hi Joe,

Could you please contact the ECB maintainer and ask? Since CEDET is
now beeing merged into Emacs difficulties like these are expected
during that process, but perhaps he is not aware (though I doubt it).
Please contact me again after this. I can upload a new version of
Emacs+EmacsW32 if that will solve your problem.

On Mon, Nov 2, 2009 at 9:28 PM, Joe Jones <darkdescendant <at> gmail.com> wrote:
> I am trying to get ecb working on my Win 7 box but am having quite a bit of
> difficulty, mostly due to cedet. After a lot of digging around it turns out
> that cedet is included with the distribution (EmacsW32 emacs build 23.1).
> However, there are some definite differences over what ecb is expecting.
> First off, according to the cedet site, a simple setup is as below:
>
> (global-ede-mode 1)                      ; Enable the Project management
> system
> (semantic-load-enable-code-helpers)      ; Enable prototype help and smart
> completion
> (global-srecode-minor-mode 1)            ; Enable template insertion menu
>
> global-ede-mode works fine, but none the other calls fail. It turns out that
> neither semantic nor srecode are loaded by cedet as expected. I can add a
> set of require lines for each ( (require 'semantic) (require 'srecode) ) in
> my .emacs file which seems to load fine. However, neither of those functions
> appears to be available.
> Given this I still tried to get ecb 2.40 to work so I installed it into
> Emacs/emacs/site-lisp and added the appropriate load-file and require lines
> to my .emacs file. On load, this all fails because ecb can't find the
> semantic-ctxt package/ This seems weird but I looked around in the sources
> in cedet and lo and behold, the package names are different! semantic-ctx is
> now semantic/ctxt. In fact, all the packages that used semantic-XXXX are now
> semantic/XXX.
> On top of this, there is one package being looked for (semantic/analyze/fcn)
> that is being required in a few semantic lisp files that doesn't seem to
> actually be provided by anybody in the included cedet package.
> At this point I am at wit's end. I have no idea what to do to get ecb
> working in this version of emacs.Any help in getting this going is greatly
> appreciated.
>
> Thanx,
> joe
>

RE: Re: mouse wheel button problem on Windows

I found a solution to my mouse wheel-button problem, in case it helps others. My
mouse software is MS Intellimouse Explorer 3.0.

It turns out that there is a setting under the `Wheel' tab that actually affects
the wheel button also. Nothing I changed in the `Wheel Button' field of the
Buttons tab had any effect by itself, but this solved the problem:

1. On the `Buttons' tab, under `Wheel Button', choose `Auto Scroll'. (This is
needed, for some reason.)

2. On the `Wheel' tab, under `Wheel Troubleshooter', click the `Advanced'
button.

3. Choose the radio button `Only disable IntelliPoint wheel support for the
following programs:'

4. Click `Add', navigate to your Emacs `bin' folder and choose `emacs.exe'.

5. Repeat step four for each Emacs version that you have installed (and use).
Likewise, repeat it for `gnuclientw.exe', if you use that.

6. Sacrifice a virgin toad (any species, AFAICT) under the first full moon in
February, after playing tennis with it for 16 hours and convincing it to eat
half a bacon, lettuce, and tomato sandwich with rye toast. (The rye toast was
the hard part.)

Nothing else seemed to do the trick, but that did.

HTH.

Opening a frame on a second monitor

I've been searching for a command that allows me to open a frame on a 
second monitor on WinXP. I recall that I even succeeded once, but don't 
know what I did (or if I was dreaming).

I want a "make-frame-on-display" command that works on Win32 (the 
existing "make-frame-on-display" command seems to only support X).

Suggestions?

Thanks,

Bruce

Re: Opening a frame on a second monitor

BKnoth wrote:
> I've been searching for a command that allows me to open a frame on a 
> second monitor on WinXP. I recall that I even succeeded once, but 
> don't know what I did (or if I was dreaming).
>
> I want a "make-frame-on-display" command that works on Win32 (the 
> existing "make-frame-on-display" command seems to only support X).

That's not what make-frame-on-display does.  It opens a frame on a 
different X display (ie, a different login session).  Multiple monitors 
in the same session are handled by setting the x and y offset in 
frame-parameters to position the frame where you want it, whether on X 
or on Windows.

Problems with cmdproxy and alias

Re: Opening a frame on a second monitor

On 11/4/2009 7:42 PM, Jason Rumney wrote:
> BKnoth wrote:
>> I've been searching for a command that allows me to open a frame on a
>> second monitor on WinXP. I recall that I even succeeded once, but
>> don't know what I did (or if I was dreaming).
>>
>> I want a "make-frame-on-display" command that works on Win32 (the
>> existing "make-frame-on-display" command seems to only support X).
>
> That's not what make-frame-on-display does. It opens a frame on a
> different X display (ie, a different login session). Multiple monitors
> in the same session are handled by setting the x and y offset in
> frame-parameters to position the frame where you want it, whether on X
> or on Windows.
>
>
>
>

Thanks - you answered my question. The following frame alist opens a 
frame on my second monitor when used with the make-frame function.

(setq second-frame-alist
               '((top . 0)
                 (left . -1280)
                 (width . 150)
                 (height . 56)
                 (cursor-color . "deep sky blue")
                 (background-color . "Wheat")
                 (foreground-color . "blue3")
		)
	      )

I appreciate your help, Jason.

- Bruce

Re: Opening a frame on a second monitor

On 11/4/2009 7:42 PM, Jason Rumney wrote:
> BKnoth wrote:
>> I've been searching for a command that allows me to open a frame on a
>> second monitor on WinXP. I recall that I even succeeded once, but
>> don't know what I did (or if I was dreaming).
>>
>> I want a "make-frame-on-display" command that works on Win32 (the
>> existing "make-frame-on-display" command seems to only support X).
>
> That's not what make-frame-on-display does. It opens a frame on a
> different X display (ie, a different login session). Multiple monitors
> in the same session are handled by setting the x and y offset in
> frame-parameters to position the frame where you want it, whether on X
> or on Windows.
>
>
>
>

Thanks - you answered my question. The following frame alist opens a 
frame on my second monitor when used with the make-frame function.

(setq second-frame-alist
               '((top . 0)
                 (left . -1280)
                 (width . 150)
                 (height . 56)
                 (cursor-color . "deep sky blue")
                 (background-color . "Wheat")
                 (foreground-color . "blue3")
		)
	      )

I appreciate your help, Jason.

- Bruce

RE: Re: Opening a frame on a second monitor

> Thanks - you answered my question. The following frame alist opens a 
> frame on my second monitor when used with the make-frame function.
> 
> (setq second-frame-alist
>                '((top . 0)
>                  (left . -1280)
>                  (width . 150)
                   ...

FYI - You can use (x-display-pixel-width) to pick up the `1280' value
automatically, so it is correct regardless of the current display. In the case
of yours, it will be 1280.

So you could, if you wanted, use:
(setq second-frame-alist
      `((top . 0)
        (left . ,(x-display-pixel-width))
        (width . 150)
        ...

Re: Opening a frame on a second monitor

On 11/5/2009 10:33 AM, Drew Adams wrote:
>> Thanks - you answered my question. The following frame alist opens a
>> frame on my second monitor when used with the make-frame function.
>>
>> (setq second-frame-alist
>>                 '((top . 0)
>>                   (left . -1280)
>>                   (width . 150)
>                     ...
>
> FYI - You can use (x-display-pixel-width) to pick up the `1280' value
> automatically, so it is correct regardless of the current display. In the case
> of yours, it will be 1280.
>
> So you could, if you wanted, use:
> (setq second-frame-alist
>        `((top . 0)
>          (left . ,(x-display-pixel-width))
>          (width . 150)
>          ...
>
>
>
>
Did you mean to have the "," in front of "(x-display-pixel-width)"? 
Also, the "(x-display-pixel-width)" function is in frame.el but I can't 
call it without making it interactive. What's the proper way to call a 
function that doesn't show up as an emacs command?

Thanks for your help,

Bruce