[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fw: Re: help: typing 's' on keyboard beeps

From: Berni Joss
Subject: Fw: Re: help: typing 's' on keyboard beeps
Date: Mon, 5 Nov 2001 22:38:38 +0100

As promised, here is some news about the 's'->beep conversion saga:
I found that commenting the line:
source /etc/inputrc

in the .inputrc file of my home directory "re-enabled" the lower case 's'
The file /etc/inputrc contains: ==============================

# do not bell on tab-completion
#set bell-style none

set meta-flag on
set input-meta on
set convert-meta off
set output-meta on

$if mode=emacs

# for linux console and RH/Debian xterm
"\e[1~": beginning-of-line
"\e[4~": end-of-line
"\e[5~": beginning-of-history
"\e[6~": end-of-history
"\e[3~": delete-char
"\e[2~": quoted-insert

# for rxvt
"\e[8~": end-of-line

# for non RH/Debian xterm, can't hurt for RH/DEbian xterm
"\eOH": beginning-of-line
"\eOF": end-of-line

# for freebsd console
"\e[H": beginning-of-line
"\e[F": end-of-line

== end of /etc/inputrc ============================

I hadn't time so far in further identifying the command converting all 's'
typed in octave 2.1.33 into beeps.
At first sight I see nothing offending in the /etc/inputrc file above ...
... but then I don't really understand much of it either!


On Mon, 29 Oct 2001 09:08:08 -0500
"Steve Goncalo" <address@hidden> wrote:

> No solution, but some questions...
> What kind of platform are you on?
Redhat 7.1; kernel 2.4.9-6; i586

> What version of gcc do you have?

> Are you comparing a precompiled 2.0.16

> to a 2.1.3x that you built yourself?
no; also pre-compiled and distributed by redhat

> If you create a script file "SCRIPT.m", can you use
> lowercase s in it (e.g. sin(0) )?
yes, works fine

> If so, I would suspect
> your yacc/lex parser is OK and the problem is somewhere in
> the line editing functions (readline). I have not looked,
> but I suspect there is an option to "configure" which would
> disable the line editing functions.
> Can you try running the same binary from a different user name
> just to see if there might be something in your environment setup
> that is causing trouble?
Yes! I hadn't thought of this :-((
Lower case 's' works fine from a different user ... I'will investigate further.
Will let you know what I find out.

Thank you all who responded so far,

> -----Original Message-----
> From: Berni Joss [mailto:address@hidden
> Sent: Saturday, October 27, 2001 3:37 PM
> To: address@hidden
> Subject: help: typing 's' on keyboard beeps
> Using octave 2.1.33 or 2.1.34 I am unable to type the lowercase letter 's'
> into octave's command window!
> Whenever I hit the 's' key on the keyboard octave beeps, but otherwise
> ignores
> the key code. As you would guess, this is quit annoying :-(
> Uppercase 'S' (shift-key + 's') works fine!
> octave 2.0.16 works fine.
> Anybody has any clues about what might be happening?
> Is this a known feature/bug? By the way I failed finding any list of known
> bugs
> for version 2.1.33/34; is there one?
> Any hints/help are much appreciated.
> Thanks, Berni.
> -------------------------------------------------------------
> Octave is freely available under the terms of the GNU GPL.
> Octave's home on the web:
> How to fund new projects:
> Subscription information:
> -------------------------------------------------------------

Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]