Sponsored Content
Full Discussion: System audible beep
Operating Systems Linux Slackware System audible beep Post 302483264 by slak0 on Friday 24th of December 2010 11:18:52 PM
Old 12-25-2010
System audible beep

Corona688 THANX. The problem is with #1 apparently since I had taken care of 2-3. So are you saying for #1 that I can only invoke a beep from a virtual console using echo command and must use xset in an X-window?
I have (#4?) P C Speak unmuted and set to 80% in alsamixer -c2 is that what you meant by enabling the channel?
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

no beep in shell??

hiho, who has an idea how i can tell my shell that it should not beep on errors or when i'm using the TAB in bash to complete noone needs to know when i make mistakes ;-) solaris 9 (SPARC) bash 2.05 thx a lot Preßy (1 Reply)
Discussion started by: pressy
1 Replies

2. HP-UX

Turn off awful beep

. (1 Reply)
Discussion started by: Driver
1 Replies

3. UNIX for Dummies Questions & Answers

Need to shut off beep

I need to know how to turn off the beep in my unix environment. I tried with the Common Desktop Environment on solaris but it didn't work. I used to know the environment variable to set but I have forgotten it. (1 Reply)
Discussion started by: jpedicone
1 Replies

4. UNIX for Dummies Questions & Answers

How do I make 'tail -f' beep?

Hi, I'm moniroting numerous logs in my new job (tail -f JOE.log | grep ALERT) and I want to be able to make the Terminal BEEP when ever something comes up. Is this something I can do easily? Any help with the above (or an alternative) would be appreciated, so I can stop staring at the... (1 Reply)
Discussion started by: the_big_v
1 Replies

5. Linux

the old question: how to disable the beep ?

still the old question (didn't find the satisfied answer in the forum) how to disable the awful beep in linux workstation? i tried this: /etc/inputrc -〉set bell-style none but it can only disable the beep whenever you input wrongly in the console. in some othercases, i still can hear... (1 Reply)
Discussion started by: princelinux
1 Replies

6. UNIX for Dummies Questions & Answers

How to get ride of the BEEP in Solaris

Hello, I did a search on this forum and a global search to try and find out how to disable that annoying beep that you get when you mistype or hit the esc key in VI and i didn't have that problem last week. I'm using Solaris and bash shell and i've put these commands into my .profile file: ... (2 Replies)
Discussion started by: bobk544
2 Replies

7. Ubuntu

I can't make my pc speakers beep

I don't know why, but when I issue echo -e '\a' or beep. I get only some sound, set in my OS (Ubuntu Karmic). I tried to run these on Lenovo Y510KA and Lenovo S10-2. Is there another way to make my laptops beep?.. (3 Replies)
Discussion started by: Sapfeer
3 Replies

8. Solaris

System hangs (freezes) on system bell/beep

I am running OpenIndiana development version oi_148 32-bit on a seven-year-old Dell Inspiron 8600. Seems to be running fine except for one particular annoyance: It freezes whenever a system bell/beep plays. I have mitigated this by turning the system bell off in gnome-terminal, which I use... (3 Replies)
Discussion started by: DeadBadger
3 Replies
console(n)						       Tk Built-In Commands							console(n)

__________________________________________________________________________________________________________________________________________________

NAME
console - Control the console on systems without a real console SYNOPSIS
console subcommand ?arg ...? _________________________________________________________________ DESCRIPTION
The console window is a replacement for a real console to allow input and output on the standard I/O channels on platforms that do not have a real console. It is implemented as a separate interpreter with the Tk toolkit loaded, and control over this interpreter is given through the console command. The behaviour of the console window is defined mainly through the contents of the console.tcl file in the Tk library. Except for TkAqua, this command is not available when Tk is loaded into a tclsh interpreter with "package require Tk", as a conventional terminal is expected to be present in that case. In TkAqua, this command is ony available when stdin is /dev/null (as is the case e.g. when the application embedding Tk is started from the Mac OS X Finder). console eval script Evaluate the script argument as a Tcl script in the console interpreter. The normal interpreter is accessed through the consolein- terp command in the console interpreter. console hide Hide the console window from view. Precisely equivalent to withdrawing the . window in the console interpreter. console show Display the console window. Precisely equivalent to deiconifying the . window in the console interpreter. console title ?string? Query or modify the title of the console window. If string is not specified, queries the title of the console window, and sets the title of the console window to string otherwise. Precisely equivalent to using the wm title command in the console interpreter. ACCESS TO THE MAIN INTERPRETER
The consoleinterp command in the console interpreter allows scripts to be evaluated in the main interpreter. It supports two subcommands: eval and record. consoleinterp eval script Evaluates script as a Tcl script at the global level in the main interpreter. consoleinterp record script Records and evaluates script as a Tcl script at the global level in the main interpreter as if script had been typed in at the con- sole. ADDITIONAL TRAP CALLS
There are several additional commands in the console interpreter that are called in response to activity in the main interpreter. These are documented here for completeness only; they form part of the internal implementation of the console and are likely to change or be mod- ified without warning. Output to the console from the main interpreter via the stdout and stderr channels is handled by invoking the tk::ConsoleOutput command in the console interpreter with two arguments. The first argument is the name of the channel being written to, and the second argument is the string being written to the channel (after encoding and end-of-line translation processing has been performed.) When the . window of the main interpreter is destroyed, the tk::ConsoleExit command in the console interpreter is called (assuming the con- sole interpreter has not already been deleted itself, that is.) DEFAULT BINDINGS
The default script creates a console window (implemented using a text widget) that has the following behaviour: [1] Pressing the tab key inserts a TAB character (as defined by the Tcl escape.) [2] Pressing the return key causes the current line (if complete by the rules of info complete) to be passed to the main interpreter for evaluation. [3] Pressing the delete key deletes the selected text (if any text is selected) or the character to the right of the cursor (if not at the end of the line.) [4] Pressing the backspace key deletes the selected text (if any text is selected) or the character to the left of the cursor (of not at the start of the line.) [5] Pressing either Control+A or the home key causes the cursor to go to the start of the line (but after the prompt, if a prompt is present on the line.) [6] Pressing either Control+E or the end key causes the cursor to go to the end of the line. [7] Pressing either Control+P or the up key causes the previous entry in the command history to be selected. [8] Pressing either Control+N or the down key causes the next entry in the command history to be selected. [9] Pressing either Control+B or the left key causes the cursor to move one character backward as long as the cursor is not at the prompt. [10] Pressing either Control+F or the right key causes the cursor to move one character forward. [11] Pressing F9 rebuilds the console window by destroying all its children and reloading the Tcl script that defined the console's be- haviour. Most other behaviour is the same as a conventional text widget except for the way that the <<Cut>> event is handled identically to the <<Copy>> event. EXAMPLE
Not all platforms have the console command, so debugging code often has the following code fragment in it so output produced by puts can be seen while during development: catch {console show} SEE ALSO
destroy(n), fconfigure(n), history(n), interp(n), puts(n), text(n), wm(n) KEYWORDS
console, interpreter, window, interactive, output channels Tk 8.4 console(n)
All times are GMT -4. The time now is 09:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy