impossible to leave a shell frame with C-o

impossible to leave a shell frame with C-o

[paragoge]

This is my first posting, here. 
With two opened frames, I normally move to the other with C-o, but this is
impossible from a shell frame.
Is there a special shortcut?
Thank you. 
-- 
View this message in context: http://old.nabble.com/impossible-to-leave-a-shell-frame-with-C-o-tp30903898p30903898.html
Sent from the Emacs - Help mailing list archive at Nabble.com.

Re: impossible to leave a shell frame with C-o

[Peter Dyballa]

Am 11.02.2011 um 19:39 schrieb paragoge:

> With two opened frames, I normally move to the other with C-o, but  
> this is
> impossible from a shell frame.


What you call "frames" are obviously the windows in one frame. By  
typing C-h k you can type in mini-buffer C-o and see what it actually  
means in your window's mode – I presume it's open-line. (I usually  
change to another window with C-x o or Fn-RET – my customisation.)

--
Greetings

   Pete

Don't force it; get a larger hammer.
				– Anthony's Law of Force

Re: impossible to leave a shell frame with C-o

[Tim X]

paragoge <christophe@johann-brass.eu> writes:

> This is my first posting, here. 
> With two opened frames, I normally move to the other with C-o, but this is
> impossible from a shell frame.
> Is there a special shortcut?
> Thank you. 

Its important to try and stick with standard emacs terminology when
asking for help to avoid confusion. In emacs, Frames are what many other
systems call windows and windows are the buffer display area within a
frame. You can have multiple frames and each frame can have multiple
windows. From your description, it sounds like your probably talking
about windows rather than frames. 

The standard definition of C-o is open-line. Therefore, your setup must
have modified the standard key bindings in either your .emacs file or a
site wide initialisation file or your running one of the 'ergonomic'
packages which remap many of the standard key bindings. 

The standard binding for other-window is C-x o. Many people don't
realise that emacs actually has an underlying philosophy/theme to how it
binds commands to keys. For example, many of the buffer/window/frame
related commands are bound to a C-x prefix. I would first see if C-x o
is bound to other-window while in shell mode.

For shell mode (i.e. M-x shell), C-o is normally bound to
switch-to-completions (at least in Emacs 24.0.50). 

Two very useful commands to diagnose problems relating to key bindings
are

C-h b (list all the key bindings for the current buffer)
C-h k (list key bindings for a specific key)

An error people sometimes make when re-mapping key bindings is that they
do a global key binding. However, many modes will setup their own mode
specific key bindings, which will override the global definitions. some
of the packages that attempt to re-map standard emacs key bindings
either overlook this or require you to setup mode specific bindings
within one of the modes startup hooks.

You need to work out what is bound to C-o in your shell mode buffer (use
C-h k) and then decide if you need that binding. If you don't, you can
probably unbind the existing definition and re-bind it to other-window
in one of the mode's load/startup hooks. Alternatively, you may still be
able to use the standard definition of C-x o while in shell mode. 

Note that if you do rebind some keys, rememer that some modes, like
shell mode, have some restrictions because the interpreter will attempt
to consume some key sequences (such as C-c).

Tim
-- 
tcross (at) rapttech dot com dot au

Re: impossible to leave a shell frame with C-o

[paragoge]

Sorry for the confusion with the terminology (or with other things. I am
beginning with emacs ans this is unavoidable ). Yes, I mean "other window"
and not "other frame". As I get with the command ls in the shell (Mx-shell)
such signs as  ^[[01;34mIED[, I have then used the bash (M-x term) and from
here, the keys bindings C-x o (or any others beginning with C-x) doest have
any effect. From the shell (Mx-shell), C-x o works.
-- 
View this message in context: http://old.nabble.com/impossible-to-leave-a-shell-frame-with-C-x-o-tp30903898p30914101.html
Sent from the Emacs - Help mailing list archive at Nabble.com.

Re: impossible to leave a shell frame with C-o

[Peter Dyballa]

Am 13.02.2011 um 13:34 schrieb paragoge:

> I have then used the bash (M-x term) and from
> here, the keys bindings C-x o (or any others beginning with C-x)  
> doest have
> any effect.


That's correct and documented. For beginners the Help menu contains a  
few useful items. Possibly in the right top-down sequence.

The "^[[01;34m" texts are ANSI Escape Sequences to colourise the  
output of (g)ls. You can switch that off. Or execute ansi-color-for- 
comint-mode-on. For example in your init file.

--
Greetings

   Pete

"Debugging? Klingons do not debug! Our software does not coddle the  
weak."

Re: impossible to leave a shell frame with C-o

[paragoge]

Peter Dyballa wrote:
> 
> The "^[[01;34m" texts are ANSI Escape Sequences to colourise the  
> output of (g)ls. You can switch that off. 
> 
Can you please say me how? 

-- 
View this message in context: http://old.nabble.com/impossible-to-leave-a-shell-frame-with-C-x-o-tp30903898p30914708.html
Sent from the Emacs - Help mailing list archive at Nabble.com.

Re: impossible to leave a shell frame with C-o

[Perry Smith]

On Feb 13, 2011, at 6:34 AM, paragoge wrote:

>  I have then used the bash (M-x term) and from
> here, the keys bindings C-x o (or any others beginning with C-x) doest have
> any effect. From the shell (Mx-shell), C-x o works.

I've never used M-x term, so I tried it.  C-x o works for me.  But then I did:

`C-h f term' to get the documentation.  It pointed me to term-mode.  In
term-mode, it tells me about line and character mode and in char mode
there is term-escape-char.  So, perhaps you have term-escape-char
set to something?  In my case, it is set to nil.  I don't fully understand
the lisp code.

HTH,
Perry

Re: impossible to leave a shell frame with C-o

[Peter Dyballa]

Am 13.02.2011 um 15:44 schrieb paragoge:

>> The "^[[01;34m" texts are ANSI Escape Sequences to colourise the
>> output of (g)ls. You can switch that off.
>>
> Can you please say me how?

See "man (g)ls" or in GNU Emacs: M-x manual-entry RET (g)ls RET –  
where "(g)ls" stands for "either gls or ls, on eof the two will work".  
You do know your UNIX system?

--
Greetings

   Pete

I wouldn't recommend sex, drugs or insanity for everyone, but they've  
always worked for me.
				– Hunter S. Thompson

Re: impossible to leave a shell frame with C-o

[paragoge]

Peter Dyballa wrote:
> 
> 
> Am 13.02.2011 um 15:44 schrieb paragoge:
> 
>>> The "^[[01;34m" texts are ANSI Escape Sequences to colourise the
>>> output of (g)ls. You can switch that off.
>>>
>> Can you please say me how?
> 
> See "man (g)ls" or in GNU Emacs: M-x manual-entry RET (g)ls RET –  
> where "(g)ls" stands for "either gls or ls, on eof the two will work".  
> You do know your UNIX system?
> 
No, I dont.
The man for ls says : with --color[WHEN] (WHEN may be 'never', 'always' or
'auto'. Is that the adequate entry for switching off the colorize?
I have a little experimented...for example with ls -d and I have got
:^[[0m^[[01;34m.^[[0m ??!!

-- 
View this message in context: http://old.nabble.com/impossible-to-leave-a-shell-frame-with-C-x-o-tp30903898p30915219.html
Sent from the Emacs - Help mailing list archive at Nabble.com.

Re: impossible to leave a shell frame with C-o

[Peter Dyballa]

Am 13.02.2011 um 17:28 schrieb paragoge:

> The man for ls says : with --color[WHEN] (WHEN may be 'never',  
> 'always' or
> 'auto'. Is that the adequate entry for switching off the colorize?

Exactly: use NEVER when Emacs. This can be achieved by ~/.emacs_<the  
name of your login shell> – see documentation!

> I have a little experimented...for example with ls -d and I have got
> :^[[0m^[[01;34m.^[[0m ??!!


The ANSI codes intensify the brightness and switch on green (34), I  
think. At the end of the line it's all switched off for normal use.  
Would you do it differently?

The ANSI escapes are (were) documented – in additional documentation  
for Xterm and also in the Bash Prompt HOWTO. At least in last  
millennium.

--
Greetings

   Pete

One-Shot Case Study, n.:
	The scientific equivalent of the four-leaf clover, from which it is  
concluded all clovers possess four leaves and are sometimes green.

Turning off ls colors (was: impossible to leave a shell frame ...)

[Steve Revilak]

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

>The "^[[01;34m" texts are ANSI Escape Sequences to colourise the
>output of (g)ls. You can switch that off. Or execute ansi-color-for-
>comint-mode-on. For example in your init file.

In many cases, ls gets coloring information from the environment
variable LS_COLORS.  From a shell prompt, you can examine the value of
this variable by

   echo $LS_COLORS

if LS_COLORS has a value, you can try unsetting the variable, to see
what effect that has

   unset LS_COLORS

ls is not the only program that uses escape sequences for
colorization.  For example, there are distributions that use escape
sequences to colorize the the shell prompt.  bash's command prompt
comes from the environment variable $PS1; tcsh uses the environment
variable $prompt.  You may want to look at these variables as well.

Steve

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]