Rlwrap backspace issue

I am using rlwrap with SQLplus so that I make use of the arrow keys. But, the problem is that, after I type "host" so that I can use OS commands in SQLplus, the backspace key doesn't work properly. Does anybody know if there is a way around?

try
SQL> host yourcommand.shinstead of
SQL> host
$ yourcommand.sh
$ exit

Similar Messages

Backspace Issue

I have been trying to look into this issue for at least three weeks, so please bear with me if should have posted this in another forum.
I connected my mac keyboard/mouse into a KVM switch so I can switch between my Mac laptop and custom tower when I need. Just recently, the regular delete key doesn't delete as the "backspace" key would. I have a 'Delete' and 'Forward Delete' key, but both erase in the same direction. I don't have this problem when I don't use my external keyboard, or when I switch to my tower with the same keyboard. It only happens with my Mac. Any suggestions?

I have experienced the same with other Xperias, its not your phone its the website itself, as you can see at the bottom of this page its powered by Lithium, that's something they have to address.
"I'd rather be hated for who I am, than loved for who I am not." Kurt Cobain (1967-1994)

Ctrl-Alt-Backspace issue with Fluxbox and SLiM

Hi folks :)
I'm pretty new to Arch, had a few attempts at installing it in the past but wasn't quite ready and so decided to expand my Linux knowledge a little more, first. Well, I've done that and now I'm having another go, and things are going quite well. However, I have one minor problem. In ~/.xinitrc, I have the line 'exec startfluxbox' to start Fluxbox and do everything that is contained within the ever-so-handy 'startfluxbox' file. That works perfectly. However, if I restart X by pressing the Ctrl-Alt-Backspace combination, I'm sent to the command line rather than SLiM. However, if I replace 'exec startfluxbox' with 'exec fluxbox' it works fine and brings me straight back to the SLiM login window. Of course, I then can't make use of the 'startfluxbox' file.
Could anybody shed some light on why this might be happening? I know it's more than likely going to be something simple that I've missed, but any help would be appreciated. :)
Thanks,
Joel.

And using fluxbox instead of startfluxbox still works? Strange.
I had the same problem as well with slim and Xfce (sometimes SLiM would respawn after some minutes if I logged out normally), and ended up just giving up on SLiM.
I'll give it a try with my openbox-setup (should be similar enough to the fluxbox way).
What happens if you log out of your session instead of killing the xserver?
You could always give some other login manager a try, kdm/gdm or qingy if you want things lite.
[edit: I tried it, SLiM works fine with openbox-session. It needs rather a lot of time to start up after booting but that might have something to do with me having backgrounded daemons rather indiscriminately.
Probably a stupid idea, but have you tried waiting a bit? As I've mentioned, sometimes SLiM took a few minutes to respawn due to some bug or other.
Last edited by lastchancetosee (2009-05-16 20:51:31)

Command+backspace issue

Hi there,
I've been trying to send files to the trash through the command+backspace shortcut, but from some days 'till now, it only says to me that the file will be deleted immediately (with a confirmation dialog box), instead.
I've defaulted all of the shortcut options in the prefs panel, and can't find anything else on the web to solve this. I'd like the shortcut as it was!
Thanks in advance!

IE7 Backspace issue

If you are writing some text in a inputfield somewere in
shockwave and then you press backspace you jump to the previous
site. Is there any workaround for that "bug"?

You might have to use javascript in the web page to trap or
disable the
backspace key. Another possibily would be to spawn a new
browser window and
load your shockwave into that, then there will be no where
for it to go back
to.
Timm
"the real POTMO" <[email protected]> wrote
in message
news:esr86l$a5q$[email protected]..
> If you are writing some text in a inputfield somewere in
shockwave and
> then you press backspace you jump to the previous site.
Is there any
> workaround for that "bug"?

Backspace issues in terminal

Hi
I seem to reacall someone mentioned this before but I cant seem to find it in the archive.
I have set my locale to sv_SE.UTF-8 and all is well..almost
When in a terminal session and having my terminal also set to UTF-8 when i type an umlaut, for instance ä and do a backspace to delete the letter then the terminal will also delete one character of the prompt.
hence if the prompt is
user@machine /Library/Webserver/cgi-executables $
and i type ä
i.e
user@machine /Library/Webserver/cgi-executables $ä
and then do a backspace to get rid of ä and get the cursor to the beginning of the line I end up with
user@machine /Library/Webserver/cgi-executables
thus the $ in the cursor has been removed..if I had put three umlauts I would have had the characters removed when backspacing.
I'm using bash ofcourse and xterm-color with the following .inputrc
set meta-flag on
set convert-meta off
set output-meta on
set completion-ignore-case on
set show-all-if-ambiguous on
Anyone have any ideas?

Sorry, I can't think of what is wrong in your environment. I guess your bash is the same as mine.
-rwxr-xr-x 1 root wheel 581636 21 Mar 2005 /bin/bash
In Unicode, 'ä' can be represented in two different ways; precomposed and decomposed. In the precomosed form, 'ä' is represented by a single character, while in the decomposed form by 'a' + 'umlaut super-imposed on the preceding character'. If I enter 'ä' from my keyboard by "option+u a" the I get the precomposed character. On the other hand, MacOS X file system uses decomposed form for filenames, so if I get 'ä' as a part of a filename by completion (by hitting TAB), then it is in the decomposed form.
But, in both cases, the backspace key works normally in my environment.
In the case of precomposed char, a single backspace erases the 'ä' and leaves the prompt.
In the case of decomposed char, a single backspace erases only the umlaut, leaving a plain 'a' (if I hit return here, then I get "bash: a: command not found"). If I hit the second backspace, then the 'a' is erased and just the prompt remains.
How do you enter 'ä'? Are you using Swedish keyboard? You can find whether your 'ä' is precomposed or decomposed by
bash% echo ä > foo
bash% od -xc foo
You will get 'c3 a4' for precomposed and '61 cc 88' for decomposed form.
PowerMac G4 Mac OS X (10.4.3)

AR9.1 Rich Media Annotation TextInput and Backspace Key

I've put together a test PDF see:
http://www.amrita-cfd.org/4adobe/rich-media/shock-tube.pdf
that shows that the backspace key does not work as expected
for an a TextInput field in a rich-media annotation when
viewed with Linux AR9.1; at least not with my SuSE 10.3 setup.
There are a couple of other issues not alluded to in the test PDF:
(i) the /Widget used to toggle the attachments pane does not work
in fullscreen mode; (ii) the /Widget used to zoom out from
the rich-media annotation has /Normal, /Rollover and /Down
appearances, but only the /Normal appearance is drawn.
James Quirk

Hi Sandip,
Thanks for your reply. I'm glad to hear that the backspace
issue is being worked on and I'm guessing that you're
also aware of a similar problem with the enter key?
I agree that my non-Acrobat PDF might be deficient in some
way and it's also possible that my user preferences are
not quite right. But consider the following.
I re-jigged the test PDF such that the /Widget whose /R
and /D appearances were not activated now lies half on
the rich-media SWF and half on the background page.
Recall this is the /Widget that reads "Click to zoom out!",
which appears when the SWF is activated.
Interestingly, when I position the mouse over the /Widget
half that lies off the SWF (the right-hand half) then the
right-hand half does have its /R and /D appearances rendered.
But the left-hand half, the part that lies over the SWF,
is stuck with the /N appearance.
Following this observation, I re-jigged the /Widget to
print out the events its receives on the JS console.
And it seems that the left-hand half of the /Widget
is not getting /E or /X events, even though the
mouse correctly changes shape, but it does receive
/D, /Fo, /U and /Bl events. The right-hand half
receives all events as normal.
You can also try the following. Move the mouse over
the right-hand half of the /Widget, such that an
/E event is generated. Then move the mouse along
the /Widget towards the left-hand half: the second
the mouse reaches the left-hand half the /Widget
receives an /X event.
Therefore it looks like there is some inconsistency
in the event model when a /Widget lies on top of
a rich media annotation, or at least the behaviour
I'm observing is not hinted at in the document adobe_supplement_iso32000.pdf which covers rich-media
annotations.
Anyhow, I'll send you the original PDF as you requested
along with the modified one I describe above.
Regards,
James
p.s. For anyone else reading this message, I've posted
the modified PDF at:
http://www.amrita-cfd.org/4adobe/rich-media/shock-tube-v2.pdf

W520 Keyboard: Noisey (Backspace)-Key

A few weeks into using (well, configuring more than using, at this point) my new W520, I've become increasingly aware of (read: annoyed by) the sound (and feel) of my (Backspace)-key. It has a wee bit of a clatter to it. Given another thread I just read,‡ I guess I should count myself fortunate: other than the Backspace issue, I have no complaints about the keyboard.
One thing worth noting about the clatter sound(/feel): it occurs on the release of the key; not on the downward keystroke.
Another interesting point, a curious point, indeed, is that the clatter seems to vary a bit with repeated keystrokes; sometimes, there's no clatter at all. But usually, there's some... and again, the actual sound and feel of the key (upon release) varies a bit with repeated strokes.
Maybe this last point (the variation) wouldn't seem so odd to me if I understood the actual mechanics involved; i.e., the physical attributes of the mechanism.
In any case, I guess what I'm really looking for is any kind of feedback or suggestions.
Apparently, there's a way to lift up the keyboard (which I guess one has to do in order to add memory), and maybe if I did that, I'd discover some small piece of debris or something that's causing the problem.
Because the sound occurs on the upstroke, I'm thinking (perhaps, wishfully) that what I'm experiencing doesn't mean the longevity of the key's proper functioning is compromised. So, it's not so much that I'm concerned about key failure as I'm just annoyed by the sound.
Well, I guess that's it. It's the middle of the night, and beyond this, I'll just ramble.
So... any thoughts? I'm open to anything... including "Don't sweat the small stuff; you should just live with it." ...OR... on the other end of the spectrum: "If worse comes to worse, you could always swap in a new keyboard." Could I?
Okay... thanks.
--Thri
‡ Although, this thread is three and a half years old and pertains to the W500.

Thanks. Your suggestion is helpful.
Two questions:
Would I have to send my entire laptop in? ... or could they just send me a new keyboard?
If the latter (Lenovo sends me a new keyboard), is this something I should be able to do myself (predicated on finding some kind of how-to reference materials, etc.)?
Thanks again.
--Thri

URXVT Title issue and keybind issue (backspace, delete, etc.)

Hi,
Two questions:
1) I use zsh. How can I set the title of urxvt to be my current directory?
2) I'm having an issue in urxvt wih backspacing/deleting/end-of-line/beginning-of-line. What are the proper bindkey's for that?

Here's straight from my ~/.zshrc file
# This sets the window title to the last run command.
[[ -t 1 ]] || return
case $TERM in
*xterm*|rxvt|(dt|k|E|a)term)
preexec () {
print -Pn "\e]2;$1\a"
screen*)
preexec () {
print -Pn "\e\"$1\e\134"
esac
# Setting HOME and END keys
case $TERM in (xterm*|aterm|rxvt)
bindkey '\e[H' beginning-of-line
bindkey '\e[F' end-of-line ;;
esac
The preexec codes actually print out my last command.
So, in order for it to do what you want, you would need to change:
case $TERM in
*xterm*|rxvt|(dt|k|E|a)term)
preexec () {
print -Pn "\e]2;$1\a"
to:
case $TERM in
*xterm*|rxvt|(dt|k|E|a)term)
preexec () {
print -Pn "\e]2;%~\a"
That should do it for ya.
Last edited by Knute (2009-09-06 00:57:18)

HD Grinds When i hit 'enter' or 'backspace' - XFS issue?

I have had the same sata drive for a few years now, and i install and reinstall all the time, so I may have just worn teh drive out. But, i recently tried using the XFS file system, and now when i hit my enter key or the backspace key on the keyboard the drive grinds and grinds and the PC almost locks up, it will then stop after a minute, and everyhting is back to normal, could this be a XFS issue, or probably bad hardware? htop shows my cores as only be 0-1% used, and ram is only using 54mb - so Its a nice system with no real stress on it. If there is anysort of 'spinrite' program for linux, I could try testing the drive, but I have only found a dd'something' program, and Im not sure if its what im looking for. Any ideas or thoughts would be awesome, im strapped for cash, so I hope its not the drive

alright I installed, and enabled 'smart' (whatever that is ) and then ran a short self test, then ran the command you had posted. Here are the outputs.
justin ~ $ sudo smartctl --log=selftest /dev/sdb
smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 14568 -
sudo smartctl -a /dev/sdb
smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.8 family
Device Model: ST3250823AS
Serial Number: 5ND0H7BX
Firmware Version: 3.03
User Capacity: 250,058,268,160 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Tue May 20 17:38:21 2008 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 430) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 84) minutes.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 053 047 006 Pre-fail Always - 231310844
3 Spin_Up_Time 0x0003 099 098 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 163
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 088 060 030 Pre-fail Always - 784831267
9 Power_On_Hours 0x0032 084 084 000 Old_age Always - 14568
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 169
194 Temperature_Celsius 0x0022 027 051 000 Old_age Always - 27 (Lifetime Min/Max 0/10)
195 Hardware_ECC_Recovered 0x001a 053 046 000 Old_age Always - 231310844
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 88 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 88 occurred at disk power-on lifetime: 13519 hours (563 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
10 51 01 2e 51 1c ed
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
37 00 01 2e 51 1c ed 00 1d+05:11:07.877 SET MAX ADDRESS EXT
27 00 00 2e 51 1c e0 00 1d+05:10:58.895 READ NATIVE MAX ADDRESS EXT
37 00 00 2e 51 1c ed 00 1d+05:10:58.861 SET MAX ADDRESS EXT
27 00 01 2e 51 1c e0 00 1d+05:10:58.861 READ NATIVE MAX ADDRESS EXT
37 00 01 2e 51 1c ed 00 1d+05:10:58.832 SET MAX ADDRESS EXT
Error 87 occurred at disk power-on lifetime: 13519 hours (563 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
10 51 01 2e 51 1c ed
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
37 00 01 2e 51 1c ed 00 1d+05:11:07.877 SET MAX ADDRESS EXT
27 00 00 2e 51 1c e0 00 1d+05:10:58.895 READ NATIVE MAX ADDRESS EXT
37 00 00 2e 51 1c ed 00 1d+05:10:58.861 SET MAX ADDRESS EXT
27 00 01 6f 59 1c e0 00 1d+05:10:58.861 READ NATIVE MAX ADDRESS EXT
29 00 01 6f 59 1c e0 00 1d+05:10:58.832 READ MULTIPLE EXT
Error 86 occurred at disk power-on lifetime: 13519 hours (563 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
10 51 01 2e 51 1c ed
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
37 00 01 2e 51 1c ed 00 1d+05:10:38.111 SET MAX ADDRESS EXT
27 00 00 2e 51 1c e0 00 1d+05:10:45.213 READ NATIVE MAX ADDRESS EXT
37 00 00 2e 51 1c ed 00 1d+05:10:45.213 SET MAX ADDRESS EXT
27 00 01 2e 51 1c e0 00 1d+05:10:45.086 READ NATIVE MAX ADDRESS EXT
37 00 01 2e 51 1c ed 00 1d+05:10:45.086 SET MAX ADDRESS EXT
Error 85 occurred at disk power-on lifetime: 13519 hours (563 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
10 51 01 2e 51 1c ed
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
37 00 01 2e 51 1c ed 00 1d+05:10:38.111 SET MAX ADDRESS EXT
27 00 00 2e 51 1c e0 00 1d+05:10:38.111 READ NATIVE MAX ADDRESS EXT
37 00 00 2e 51 1c ed 00 1d+05:10:37.621 SET MAX ADDRESS EXT
27 00 01 6f 59 1c e0 00 1d+05:10:37.621 READ NATIVE MAX ADDRESS EXT
29 00 01 6f 59 1c e0 00 1d+05:10:37.620 READ MULTIPLE EXT
Error 84 occurred at disk power-on lifetime: 13504 hours (562 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
10 51 01 2e 51 1c ed
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
37 00 01 2e 51 1c ed 00 14:08:10.847 SET MAX ADDRESS EXT
27 00 00 2e 51 1c e0 00 14:08:10.720 READ NATIVE MAX ADDRESS EXT
37 00 00 2e 51 1c ed 00 14:08:10.720 SET MAX ADDRESS EXT
27 00 01 2e 51 1c e0 00 14:08:10.504 READ NATIVE MAX ADDRESS EXT
37 00 01 2e 51 1c ed 00 14:08:10.503 SET MAX ADDRESS EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 14568 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
sudo grep sdb /etc/fstab
/dev/sdb1 /boot ext2 defaults 0 1
/dev/sdb2 swap swap defaults 0 0
/dev/sdb3 / xfs defaults 0 1
/dev/sdb4 /home xfs defaults 0 1
If you need me to run any other commands etc, I can do that no problem. I am running a long test now, and will post its results when I go home for lunch.
Last edited by axion419 (2008-05-21 13:22:42)

Wireless Keyboard Issues - Backspace not behaving

this is driving me insane.
Ive spent hoours lookign for a solution and it's making it almost impossible to get on with any work.
Everything was fine, never had any problems.
then I changed the batteries on the keyboard. I think i went from one set of recharageables to another.
the biggest frustration is the behaviour of the backspace key, which does nopt backspace and delete as it should.
It now deletes to the left!
Also the arrows do not behave as they used to do and I'm unable to type a capital t.
I've tried everything, i.e. turnign it on and off, re-pairing, going through the keyboard settings, resoring everything to default etc etc
Keyboard operation reverts to normal operation if I turn it off and on , but only for a few minutes.
I thoughth it might be something to do with the rechargeable batteries, so replaced them with alkaline. - no effect.
HELP!!
the only clue that something might be wrong is, when Ive done some kind of keyboard key test where you are shown a layoput of the keyboard and it highlights the key you are pressing. he keyboard map shows the arrow on the backspace key to be facing in the opposite way to the way it actually is!
Also Ive noticed the bluetooth symbol at the top of the screen has the 3 dots horizontal - which i thought indicated low battery, but the battery is fine as Ive just replaced them.

Hello cjb222,
I would be concerned too some of the keys on my keyboard were not working. I found an article that can assist with troubleshooting issues with the built in keyboard. I recommend following the steps under the section titled, "Some keys don't work as expected" in the following article:
One or more keys on the keyboard do not respond
http://support.apple.com/kb/ts1381
Thank you for posting in the Apple Support Communities.
Best,
Sheila M.

X11 issue: e key is mapped to backspace in X11 apps

I've had this problem before but can't remember what I did to get it fixed...
I ssh into my office linux machine to launch firefox and have it displayed on my Mac Pro here at home. This works fine. The one problem I have is that when working with firefox (via ssh, displaying on my Macs X11) the "e" key is mapped to backspace.
Office machine is Ubuntu 8.04 LTS Desktop, with firefox 3 beta. I guess I'll try Opera too...
Any ideas?

This is most likely to an errant "xmodmap" somewhere in the shell init scripts on the Linux box. If you can run "xev" on the Mac you should be able to see which keycode the "e" key is generating. If you then look through the shell init scripts on the Linux side, you'll likely find that this keycode is being remapped to the backspace.
To make matters worse, this remapped key doesn't just apply to the X clients invoked via that particular ssh session, it will affect all X clients running on your Mac.
What I would suggest is modifying your init scripts on the Linux side so that they never invoke xmodmap for remote connections. The syntax depends on the shell you use, but it will be something similar to this (shown for tcsh):
if (! ${?REMOTEHOST} && ${?DISPLAY} ) then
# Make sure backspace is correctly mapped
xmodmap -e "keycode 22 = BackSpace"
endif
In fact, I'll wager you have an xmodmap line almost exactly like that. I note that on my FreeBSD machine keycode 22 is what my backspace key generates, but on my Mac keycode 22 is what my "e" key generates.
Yep, I've been down this road before on other operating systems. I actually thought my keyboard had gotten fried because the "t" key stopped working altogether. Turns out it was an errant xmodmap on a remote machine.
Brent

Firefox issue, backspace icon goes all the way back to the home page

Hello,
This behavior is consistent.
IE 8 browser - back icon goes back 1 screen
Firefox 3.0.3 - back icon goes back X number of pages to the home page. The only way I have found to go back 1 page is to click on the directory path:
ex.
Expert Forums » Community Discussions » Suggestions and Comments
To go back one level I would have to click on
Suggestions and Comments.
Thanks
Bruce

Hi Bruce;
I'm using the same FF version...But haven't got the related problem...
Greetings,
Blag.

Inputrc, rlwrap, vi mode ... oh my

Howdy all,
I am trying to get vi mode editing in some of my command-line apps (python and sqlplus being my chief concerns).
I am OH ... so ... close ...
I installed rlwrap via MacPorts (rlwrap version 0.24)
Type "rlwrap python" and everything works as expected ... I can backspace, up arrow, even ctl-b and others. But I'm a vi guy.
So I create .inputrc with only "set editing-mode vi" and once again start python with "rlwrap python" ...
... and, with one minor exception, everything works. <Esc> and I'm in command mode, k ^ $ b all work like I would hope.
The minor exception is actually not so minor. All input is echoed twice. So if I type the following in python
\>>> import re
and nothing else, my screen now displays
\>>> import re
\>>> import re
Any input is echoed twice (both in python and sqlplus). Thoughts? am I missing some arcane set command ... I'm still reading "man 3 readline" to no avail.

Hmmm, interestingly, I tested your suggestion on my home mac ... before I'd checked to see if I could replicate the bug.
The difference, it seems, is that on my home Intel Mini, within python, I can "import readline" ... on my work Intel MacBook Pro I cannot. Some earlier research indicated this may be an issue.
It now seems that I always had readline support for the Mini. It is hard to tell exactly, but if I "sudo uninstall rlwrap" and "rm .inputrc" I can do basic readline support in the python interpreter, including ctl-a and ctl-e movements. If I restore my .inputrc, I get vi options ... no need at all for rlwrap.
Whereas on my MBP, even back arrow would put up uglychars. Using rlwrap would fix that at the expense of the double output.
It seems, somehow, my python distributions (python24 and python25 from MacPorts and Apple's python2.3) all lack the ability to import readline. Perhaps this isn't a python issue at all, but a system issue. Perhaps I'm missing some core functionality on my MBP that my Mini has (header? dylib? out of my expertise).

Text Message incomplete or missing? Also-SMS editing / backspace malfunction...

First issue - sometimes I received text messages that are missing the last few words/characters. I don't think this is an Android or iPhone originated issue as this happens at random from people that I know have different types of phones. Sometimes the 160 character split will break up the message and send the rest in another message, but most of the time I never see the end of the message. I currently use the existing text messaging app in conjunction with the SMS pop-up. The issue was prevalent when I used Handcent and then uninstalled it to see if that was the problem. I have also uninstalled SMS pop-up to see if it was the problem with no luck. I have looked over the settings multiple times and still cannot find anything that would be causing this. Suggestions are welcome.
Second issue - when editing a text message in portrait mode I may erase multiple characters by holding down the backspace key. On occasion, the app flips out, reverts to showing the very first message that was sent or received for the contact, freezes momentarily, and then two buttons appear on the bottom giving me the option to Cancel or Delete. I will hit Cancel or use the back button on the bottom of the phone multiple times before it will return to my message, which at this point has saved as a draft. This is EXTREMELY frustrating. It does it only at random, but it seems to be getting more frequent. The only option most of the time is to go Home and then return to text messages, find my draft, and use the backspace key carefully (and one quick push at a time to erase) so as not to invoke the same issue.
I think both of these are bugs that may be inherent with this phone in particular or possibly Gingerbread...
Thanks!
-Wes

I've been having this same issue for the past few months, in my case the problem seems to be more prevalent with text messages originating from other carriers (but not always, occasional partial incoming text issues from Verizon wireless phones as well). I called technical support, followed all their advice (basic tech advice, power cycle, remove sim, reboot, etc.) and was also transferred to HTC support that recommended a hot fix, which didn't really do anything to resolve the issue, also then did a factory reset and still no resolution. Not sure what other options I have....besides waiting for a new device when I am able to upgrade. Off topic, I think its Bee S to not be able to upgrade to a new device within 2 years, when Verizon does not fully support, properly updated/hotfix, existing issues in a timely manner...why is it that we are using and outdated OS, when a new one is out and available. Another compelling argument to purchase an iPhone (on any carrier), one device, one OS.....everyone gets an update at the same time, and phone issues are rapidly resolved. I can continue my rant, but I'll leave it as is...same issues, different day and I'm sure you've all heard the same rants of frustration.

Rlwrap backspace issue

Similar Messages

Maybe you are looking for