global-set-key not global?

global-set-key not global?

[Emory Smith]

im using the following in my .emacs:

(global-set-key "\C-j"  'bs-cycle-next)
(global-set-key "\M-j"  'bs-cycle-previous)

but a number of major modes still seem to have C-j bound to 
insert-newline.
it works fine if i use local-set-key inside the add-hook for every 
mode, but seems like i shouldnt have to do this.


also, how can i use the semicolon in a keybinding. obviously, the 
following doesnt work:

(global-set-key "\C-;"  'indent-for-comment)

how can i escape the ";" character so that it doesnt look like a 
comment to elisp?

Re: global-set-key not global?

[Stefan Monnier]

> im using the following in my .emacs:
> (global-set-key "\C-j"  'bs-cycle-next)
> (global-set-key "\M-j"  'bs-cycle-previous)

> but a number of major modes still seem to have C-j bound to insert-newline.
> it works fine if i use local-set-key inside the add-hook for every mode, but
> seems like i shouldnt have to do this.

Indeed.  Report those things as bugs.

> also, how can i use the semicolon in a keybinding. obviously, the following
> doesnt work:

> (global-set-key "\C-;"  'indent-for-comment)

Indeed, because C-; is not a character (contrary to C-a and a few other
such special cases) so you can't put it in a string.
Instead use the form [(control ?\;)].

> how can i escape the ";" character so that it doesnt look like a comment
> to elisp?

In your code above it should work just fine since it's inside a string.
When it's not inside a string use \ as I did above.


        Stefan

Re: global-set-key not global?

[Emory Smith]

On Feb 5, 2004, at 12:35 PM, Stefan Monnier wrote:

>> im using the following in my .emacs:
>> (global-set-key "\C-j"  'bs-cycle-next)
>> (global-set-key "\M-j"  'bs-cycle-previous)
>
>> but a number of major modes still seem to have C-j bound to 
>> insert-newline.
>> it works fine if i use local-set-key inside the add-hook for every 
>> mode, but
>> seems like i shouldnt have to do this.
>
> Indeed.  Report those things as bugs.
>

so a local keymap entry is not supposed to override a global one?

i didnt think this was actually a bug, but was rather wondering how i 
might make a global-set-key apply to all major modes, even if they have 
their own local binding of that key (without using a hook for every 
mode).

thanks, emory

Re: global-set-key not global?

[Kai Grossjohann]

Emory Smith <emory.smith@mac.com> writes:

> On Feb 5, 2004, at 12:35 PM, Stefan Monnier wrote:
>
>>> im using the following in my .emacs:
>>> (global-set-key "\C-j"  'bs-cycle-next)
>>> (global-set-key "\M-j"  'bs-cycle-previous)
>>
>>> but a number of major modes still seem to have C-j bound to
>>> insert-newline.
>>> it works fine if i use local-set-key inside the add-hook for every
>>> mode, but
>>> seems like i shouldnt have to do this.
>>
>> Indeed.  Report those things as bugs.
>>
>
> so a local keymap entry is not supposed to override a global one?

No.  But the global bindings for C-j and M-j should work for all
modes, so that there is no need for a mode to bind C-j and M-j itself.

So Stefan was only referring to these two keys.  For other keys, it's
different.

Kai

Re: global-set-key not global?

[Kevin Rodgers]

Kai Grossjohann wrote:
 > Emory Smith <emory.smith@mac.com> writes:
 >>On Feb 5, 2004, at 12:35 PM, Stefan Monnier wrote:
 >>>>im using the following in my .emacs:
 >>>>(global-set-key "\C-j"  'bs-cycle-next)
 >>>>(global-set-key "\M-j"  'bs-cycle-previous)
 >>>>
 >>>>but a number of major modes still seem to have C-j bound to
 >>>>insert-newline.
 >>>>it works fine if i use local-set-key inside the add-hook for every
 >>>>mode, but
 >>>>seems like i shouldnt have to do this.
 >>>
 >>>Indeed.  Report those things as bugs.
 >>
 >>so a local keymap entry is not supposed to override a global one?
 >
 > No.  But the global bindings for C-j and M-j should work for all
 > modes, so that there is no need for a mode to bind C-j and M-j itself.
 >
 > So Stefan was only referring to these two keys.  For other keys, it's
 > different.

C-j is LFD so I can understand why Emacs might treat it specially (and 
presumably C-m aka RET).  But what is the significance of M-j?

-- 
Kevin Rodgers

Re: global-set-key not global?

[Kai Grossjohann]

Kevin Rodgers <ihs_4664@yahoo.com> writes:

> C-j is LFD so I can understand why Emacs might treat it specially (and
> presumably C-m aka RET).  But what is the significance of M-j?

No, it does not have to do with the fact that C-j happens to be LFD.
It has to do with the fact that the default binding of C-j is
newline-and-indent, and that function should indent correctly in all
modes, by way of the indent-line-function variable.

M-j is bound to indent-new-comment-line by default, which reads some
variables to learn how to make a comment.  So the fix is to set the
variables so that the comment comes out right, rather than to change
the keybinding.

(Compare M-; which is comment-dwim in all modes, regardless of comment
syntax.  You don't have comment-latex, comment-c, comment-pascal, ...)

Kai