On 2013-02-26 23:40, s m wrote:
> hello all,
>
> i have problem with backspace in freebsd 8.2. when i run a serial
> program to communicate via a serial port to the other system,
> backspace shows ^? in opened terminal. i use termios and fcntl to
> open, read, write and close
hello all,
i have problem with backspace in freebsd 8.2. when i run a serial program to
communicate via a serial port to the other system, backspace shows ^? in opened
terminal.
i use termios and fcntl to open, read, write and close serial port. i set erase
and erase2 for ttyu2(my serial port
thanks Robert,
i try it before but nothing happened.
do you know how i can set erase and erase2 for stty via termios structure?
and what should be their value to backspace correct well?
On Wed, Feb 6, 2013 at 3:13 PM, Robert Bonomi wrote:
> > From owner-freebsd-questi...@freebsd.org Wed
hi all
i have problem with backspace in serial communication.
this is my scenario:
i have three box. box number 1 is windows system, number 2 is freeBSD8.2
and number 3 is cisco router. from box number 1 i connect to the box number
2 by putty and run a serial program on box number 2 that connects
> From owner-freebsd-questi...@freebsd.org Wed Feb 6 00:19:04 2013
> Date: Wed, 6 Feb 2013 09:44:37 +0330
> Subject: backspace shows ^? in serial communications
> From: s m
> To: freebsd-questions
>
> hi all
>
> i have a problem with backspace in serial communicat
box, backspace shows ^?.
now i don't know where is problem and for which system terminal settings
should be checked.
from you explanation i think that i should check serial settings in c
program in the router box. am i right?
please let me know what should i do to this program (c program in route
On Wed, 6 Feb 2013 09:44:37 +0330, s m wrote:
> hi all
>
> i have a problem with backspace in serial communications. i have a
> freebsd8.2 box with a serial card on it. when i connect to other freebsd
> box via serial port backspace does not act as i expected. backspace shows
&g
hi all
i have a problem with backspace in serial communications. i have a
freebsd8.2 box with a serial card on it. when i connect to other freebsd
box via serial port backspace does not act as i expected. backspace shows
^? on screen. i searched alot and find out that stty has two parameters
Nerius Landys writes:
> "cons25" is the native FreeBSD console (like when you're physically at
> the computer console) and xterm is of course xterm. (Side note: Why
> in the heck on my 9.0-CURRENT system the system console says the TERM
> is xterm?)
http://svn.freebsd.org/viewvc/base?view=revisi
pe Enter.
4. Type Ctrl+D.
You'll see some codes before the "0a" (because "0a" is newline).
I can't remember what I did to get the Backspace codes.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/li
On 03/25/2011 08:47 AM, Matthew Morgan wrote:
On 03/24/2011 05:55 PM, Nerius Landys wrote:
I've read a lot on the internet regarding the use of the backspace
key in
emacs, but the proposed solutions don't seem to be working for me.
I just installed FreeBSD 8.1 in Virtualbox and
On 03/24/2011 05:55 PM, Nerius Landys wrote:
I've read a lot on the internet regarding the use of the backspace key in
emacs, but the proposed solutions don't seem to be working for me.
I just installed FreeBSD 8.1 in Virtualbox and installed emacs 23.2.1 by
means of the package
> I've read a lot on the internet regarding the use of the backspace key in
> emacs, but the proposed solutions don't seem to be working for me.
>
> I just installed FreeBSD 8.1 in Virtualbox and installed emacs 23.2.1 by
> means of the package installer. Everything in
I've read a lot on the internet regarding the use of the backspace key
in emacs, but the proposed solutions don't seem to be working for me.
I just installed FreeBSD 8.1 in Virtualbox and installed emacs 23.2.1 by
means of the package installer. Everything in emacs works great e
>> ways described there to re-enable CNTL-ALT-BACKSPACE functionality
>> for the X server, and sadly I must report that for me, at least
>> _neither_ of those methods worked
>
>
>Put the following to your xorg.conf:
>
>
>Section "ServerFlags"
> Opti
On Mon, 16 Nov 2009, Philipp Lengemann wrote:
Am Sun, 15 Nov 2009 15:19:29 -0800
schrieb "Ronald F. Guilmette" :
I _did_ go and read the Handbook section that Manolis Kiagias
kindly posted a link to, and I have now tried _both_ of the two
ways described there to re-enable CNTL-ALT
Polytropon wrote:
> On Mon, 16 Nov 2009 19:35:54 +0200, Manolis Kiagias wrote:
>
>> If you stick with HAL however (using "AllowEmptyInput" bypasses the
>> autodetection), you can just use the policy file in the Handbook and
>> just add the "DontZap" option in "ServerFlags" or "ServerLayout" sec
On Mon, 16 Nov 2009 19:35:54 +0200, Manolis Kiagias wrote:
> If you stick with HAL however (using "AllowEmptyInput" bypasses the
> autodetection), you can just use the policy file in the Handbook and
> just add the "DontZap" option in "ServerFlags" or "ServerLayout" section.
Philipp Lengemann wrote:
> Am Sun, 15 Nov 2009 15:19:29 -0800
> schrieb "Ronald F. Guilmette" :
>
>
>> I _did_ go and read the Handbook section that Manolis Kiagias
>> kindly posted a link to, and I have now tried _both_ of the two
>> ways describ
Am Sun, 15 Nov 2009 15:19:29 -0800
schrieb "Ronald F. Guilmette" :
> I _did_ go and read the Handbook section that Manolis Kiagias
> kindly posted a link to, and I have now tried _both_ of the two
> ways described there to re-enable CNTL-ALT-BACKSPACE functionality
> for the
On Mon, 16 Nov 2009, Jerry wrote:
On Sun, 15 Nov 2009 21:18:36 -0700 (MST)
Warren Block replied:
It's also worth remembering that open source projects like xorg give
the users the rare privilege of being able to make a difference. Test
code, provide hardware, document bugs or fixes, do or fund
On Sun, 15 Nov 2009 21:18:36 -0700 (MST)
Warren Block replied:
>On Mon, 16 Nov 2009, Polytropon wrote:
>
>> On Mon, 16 Nov 2009 02:21:28 +0200, Manolis Kiagias
>> wrote:
>>> Just the fact that I now have to edit an xml file to simply add a
>>> Greek keyboard layout is annoying enough.
>>
>> The
On Mon, 16 Nov 2009, Polytropon wrote:
On Mon, 16 Nov 2009 02:21:28 +0200, Manolis Kiagias wrote:
Just the fact that I now have to edit an xml file to simply add a Greek
keyboard layout is annoying enough.
The fact that annoys me is that configuration seems to have
disassembled into several
On Mon, 16 Nov 2009, Polytropon wrote:
On Mon, 16 Nov 2009 01:49:04 +0200, Manolis Kiagias wrote:
By the way Xorg configuration becomes more and more elusive. Initially,
DontZap was enough. Then it had no effect at all and the fdi file was
needed. Now seems both are needed. What's next?
If t
On Mon, 16 Nov 2009 02:21:28 +0200, Manolis Kiagias wrote:
> Just the fact that I now have to edit an xml file to simply add a Greek
> keyboard layout is annoying enough.
The fact that annoys me is that configuration seems to have
disassembled into several parts that are not located in a
central
Polytropon wrote:
> On Mon, 16 Nov 2009 01:49:04 +0200, Manolis Kiagias wrote:
>
>> By the way Xorg configuration becomes more and more elusive. Initially,
>> DontZap was enough. Then it had no effect at all and the fdi file was
>> needed. Now seems both are needed. What's next?
>>
>
> If
On Mon, 16 Nov 2009 01:49:04 +0200, Manolis Kiagias wrote:
> By the way Xorg configuration becomes more and more elusive. Initially,
> DontZap was enough. Then it had no effect at all and the fdi file was
> needed. Now seems both are needed. What's next?
If this continues, I'll run my 5.4-p8 work
Ronald F. Guilmette wrote:
> Many thanks to those who responded regarding my two questions.
>
> With regards to the CNTL-ALT-BACKSPACE sequence and its ability
> (or lack thereof) to cause an immediate shutdown of the X server...
> well... I _did_ go and read the Handbook secti
Many thanks to those who responded regarding my two questions.
With regards to the CNTL-ALT-BACKSPACE sequence and its ability
(or lack thereof) to cause an immediate shutdown of the X server...
well... I _did_ go and read the Handbook section that Manolis Kiagias
kindly posted a link to, and I
that?
>
Add:
hw.syscons.kbd_reboot=0
to /etc/sysctl.conf.
Activate immediately by executing
sysctl hw.syscons.kbd_reboot=0
> 2) Prior versions of X (Xorg?) allowed CNTL-ALT-BACKSPACE to cause an
> immediate shutdown of the X server, but now, that doesn't see to work
> anymo
tionality. How do I do that?
# sysctl -d hw.syscons.kbd_reboot
hw.syscons.kbd_reboot: enable keyboard reboot
>
> 2) Prior versions of X (Xorg?) allowed CNTL-ALT-BACKSPACE to cause an
> immediate shutdown of the X server, but now, that doesn't see to work
> anymore. How can I (re-)en
ALT-DEL now causes a shutdown/reboot. (I don't
know what release this new feature started in... I only just noticed it
now.) Anyway, I'd like to know how I can disable this particular bit of
functionality. How do I do that?
2) Prior versions of X (Xorg?) allowed CNTL-ALT-BACKSPACE to cause
;linux way" and "kde/gnome way" i.e.
- adding hald as a "requirement" by default
- disabling CTRL-ALT-backspace by default - of course user should not
leave X session, it's forbidden ;)
it's not funny, because while i don't use all these KDE/gnome things, i
Wojciech Puchar wrote:
> can older Xorg server be used with just updated drivers?
> drivers are separate modules.
>
Never tried, but the way Xorg is going this looks kind of frightening ;)
___
freebsd-questions@freebsd.org mailing list
http://lists.freeb
;>> This is an answer to a question I started to post, but then decided to
>>>> research instead. I know many readers of this list use the feature I'm
>>>> describing.
>>>>
>>>> When Xorg was upgraded to version 7.4, the historic ability to sh
toric ability to shut
down X
with Control+Alt+Backspace became a non-default option. The solution to
re-enabling this behavior was to add
Option "DontZap" "off"
to the ServerLayout or ServerFlags section of xorg.conf as documented in
a note in the Handbook
http://www.freebs
list use the feature I'm
describing.
When Xorg was upgraded to version 7.4, the historic ability to shut
down X
with Control+Alt+Backspace became a non-default option. The solution to
re-enabling this behavior was to add
Option "DontZap" "off"
to the ServerLayout
4, the historic ability to shut
>> down X
>> with Control+Alt+Backspace became a non-default option. The solution to
>> re-enabling this behavior was to add
>> Option "DontZap" "off"
>> to the ServerLayout or ServerFlags section of xorg.conf as
Luke Dean wrote:
>
> This is an answer to a question I started to post, but then decided to
> research instead. I know many readers of this list use the feature I'm
> describing.
>
> When Xorg was upgraded to version 7.4, the historic ability to shut
> down X
> with C
This is an answer to a question I started to post, but then decided to
research instead. I know many readers of this list use the feature I'm
describing.
When Xorg was upgraded to version 7.4, the historic ability to shut down X
with Control+Alt+Backspace became a non-default option.
"everyone" else uses ^H for backspace - all of the BSD's and all
> > > of the vendor Unix's).
> >
> > As far as I know, ^? indicates the delete key... Maybe the
> > delete key does ^H in this setting?
>
> By "uses ^H for backspace", I was r
On Sat, May 23, 2009 at 03:03:00PM +0200, Polytropon wrote:
> On Sat, 23 May 2009 06:35:56 -0400, Thomas Dickey wrote:
> > probably (outside of Linux and a few special cases such as Cygwin,
> > "everyone" else uses ^H for backspace - all of the BSD's and all
> >
On Sat, 23 May 2009 06:35:56 -0400, Thomas Dickey wrote:
> probably (outside of Linux and a few special cases such as Cygwin,
> "everyone" else uses ^H for backspace - all of the BSD's and all
> of the vendor Unix's).
As far as I know, ^? indicates the delete key...
On Fri, May 22, 2009 at 11:04:05PM -0700, Gary Kline wrote:
> guys,
>
> here's a bug with how the backspace key doesn't work across computers.
> i'm not sure if there were troubles going from FBSD to FBSD, but there is
> when i ssh from my ubuntu platform to my ma
guys,
here's a bug with how the backspace key doesn't work across computers.
i'm not sure if there were troubles going from FBSD to FBSD, but there is
when i ssh from my ubuntu platform to my main desktop. i do this to edit
files or for replying to mutt mail using vi.
going fro
On 26/07/08 Schiz0 said:
> Hey,
>
> I have an annoying problem that I'm not sure how to solve. Here's my setup:
>
> PuTTy => My FreeBSD 6.2 box => Production FreeBSD 7.0 box
>
> All via SSH, of course. Now, on my FreeBSD 6.2 box, the backspace key
>
.vimrc on the 7.0 box:
---
set autoindent
set background=dark
set backspace=indent,eol,start
set cmdheight=2
set ignorecase
set number
set numberwidth=2
set report=0
set restorescreen=on
set ruler
set scrolloff=3
set showbreak=++
set showmatch
set showmode
set showtabline=3
Schiz0 <[EMAIL PROTECTED]> wrote:
> I have an annoying problem that I'm not sure how to solve. Here's my setup:
>
> PuTTy => My FreeBSD 6.2 box => Production FreeBSD 7.0 box
>
> All via SSH, of course. Now, on my FreeBSD 6.2 box, the backspace key
>
Hey,
I have an annoying problem that I'm not sure how to solve. Here's my setup:
PuTTy => My FreeBSD 6.2 box => Production FreeBSD 7.0 box
All via SSH, of course. Now, on my FreeBSD 6.2 box, the backspace key
works fine all the time. However, when I connect from my 6.2 box int
* Gary Kline <[EMAIL PROTECTED]> [2007-09-16 19:29:08 -0700]:
> There are Lots of thing I like about vim, but after having fouled up
> with the undo's and lost some critical writing or code, I went back to
> what I've usedsince Bill Joy pointed me at vi.
Presumably, you are talking about vi's (and
Gary Kline wrote:
On Sat, Sep 15, 2007 at 02:31:40PM -0600, Chad Perrin wrote:
On Sun, Sep 16, 2007 at 08:40:00PM +0300, Jordan Gordeev wrote:
Gary Kline wrote:
I find that if I use Settings -> Keyboard and then select
"FreeBSD Console", I come fairly close. Then [Backspac
On Sat, Sep 15, 2007 at 02:31:40PM -0600, Chad Perrin wrote:
> On Sun, Sep 16, 2007 at 08:40:00PM +0300, Jordan Gordeev wrote:
> > Gary Kline wrote:
> >
> > > I find that if I use Settings -> Keyboard and then select
> > > "FreeBSD Consol
as just until we moved into offices!) Nutshell,
I will either buy a fancyy clicky keyboard or write a CLICK
Driver.Meanehile, unless I set Konsole to ring the WAV belll,
no *ding*.
>
> > I find that if I use Settings -> Keyboard and then s
On Sun, Sep 16, 2007 at 08:40:00PM +0300, Jordan Gordeev wrote:
> Gary Kline wrote:
>
> > I find that if I use Settings -> Keyboard and then select
> > "FreeBSD Console", I come fairly close. Then [Backspace]
> > backs up, but the
en select
"FreeBSD Console", I come fairly close. Then [Backspace]
backs up, but the characters are not erased as I space
backways. UsingTerminal, it defaults to this.
Characters are not erased for me when I hit backspace in vi. In vim,
they are.
Anther indicator that
4, 2007 at 06:01:03PM -0700, Gary Kline wrote:
> > > >
> > > >>Sometimes when I ssh from a remote server and edit a file with
> > > >>vi, my [Backspace keys] are not interpretered correctly.
> > > >>Instead of eras
xterms; on my "new tao" runnning Gnome as a manager, I use
Konsole. Entrely to get the BEL in vi/nvi.
I find that if I use Settings -> Keyboard and then select
"FreeBSD Console", I come fairly close. Then [Backspace]
backs up, but the characte
On Sat, Sep 15, 2007 at 01:28:22PM -0700, Gary Kline wrote:
>
> Trying to use stty failed... .
What terminal emulator are you using? It may be that, as was the case
with me when I was using aterm, I needed to use stty *and* needed to
change a configuration in the aterm makefile. It's poss
ssh from a remote server and edit a file with
> > >>vi, my [Backspace keys] are not interpretered correctly.
> > >>Instead of erasing characters and backing up one byte and
> > >>clearing that character my cursor moves forward.
> > >>
&
wrote:
> > > > >On Fri, Sep 14, 2007 at 06:01:03PM -0700, Gary Kline wrote:
> > > > >> Sometimes when I ssh from a remote server and edit a file with
> > > > >> vi, my [Backspace keys] are not interpretered correctly.
> > > > &g
ote:
> > > >>Sometimes when I ssh from a remote server and edit a file with
> > > >>vi, my [Backspace keys] are not interpretered correctly.
> > > >>Instead of erasing characters and backing up one byte and
> > > >>
dit a file with
> > >> vi, my [Backspace keys] are not interpretered correctly.
> > >> Instead of erasing characters and backing up one byte and
> > >> clearing that character my cursor moves forward.
> > >>
> > >> Example: typing &quo
On Sat, Sep 15, 2007 at 10:58:52AM -0700, Garrett Cooper wrote:
> Chad Perrin wrote:
> >On Fri, Sep 14, 2007 at 06:01:03PM -0700, Gary Kline wrote:
> >
> >>Sometimes when I ssh from a remote server and edit a file with
> >>vi, my [Backspace keys
Chad Perrin wrote:
On Fri, Sep 14, 2007 at 06:01:03PM -0700, Gary Kline wrote:
Sometimes when I ssh from a remote server and edit a file with
vi, my [Backspace keys] are not interpretered correctly.
Instead of erasing characters and backing up one byte and
clearing that
On Fri, Sep 14, 2007 at 06:01:03PM -0700, Gary Kline wrote:
>
> Sometimes when I ssh from a remote server and edit a file with
> vi, my [Backspace keys] are not interpretered correctly.
> Instead of erasing characters and backing up one byte and
> clearing
On Sat, Sep 15, 2007 at 01:17:58AM +, Pollywog wrote:
> On Saturday 15 September 2007 01:01:03 Gary Kline wrote:
> > Sometimes when I ssh from a remote server and edit a file with
> > vi, my [Backspace keys] are not interpretered correctly.
> > Instead of e
On Saturday 15 September 2007 01:01:03 Gary Kline wrote:
> Sometimes when I ssh from a remote server and edit a file with
> vi, my [Backspace keys] are not interpretered correctly.
> Instead of erasing characters and backing up one byte and
> clearing that
Sometimes when I ssh from a remote server and edit a file with
vi, my [Backspace keys] are not interpretered correctly.
Instead of erasing characters and backing up one byte and
clearing that character my cursor moves forward.
Example: typing "Thi
:
after I login -> [press backspace] -> ^H appears -> [press DEL] -> ^? appears
in emacs -> [press backspace] -> oops, help appears
stty can translate a small set of keystrokes into functions and gets
used by the shell. In stty you can set the erase character to Ctrl-H.
The she
thought it should be is:
after I login -> [press backspace] -> ^H appears -> [press DEL] -> ^? appears
in emacs -> [press backspace] -> oops, help appears
I think Solaris was just like the above. But in my FreeBSD, things go like:
after I login -> [press backspace will erase la
-> [press backspace] -> ^H appears -> [press DEL] -> ^? appears
in emacs -> [press backspace] -> oops, help appears
I think Solaris was just like the above. But in my FreeBSD, things go like:
after I login -> [press backspace will erase last char] -> [press DEL
does the
On Sun, Aug 12, 2007 at 01:31:36PM -0500, Derek Ragona wrote:
> At 10:54 PM 8/11/2007, d.Z. wrote:
> >Hello,
> >
> >I'm a new user to FreeBSD and Unix. I used Solaris 10 last week in
> >lab, and found there is a difference between them.
> >
> >When Sol
Derek Ragona <[EMAIL PROTECTED]> writes:
> Solaris by default uses csh for user accounts.
What kind of information is this?
Solaris does _not_ use csh. Not for root and not for user accounts.
Both use 'sh' This is for solaris 10
The developers and community editions use bash for their user logins
At 10:54 PM 8/11/2007, d.Z. wrote:
Hello,
I'm a new user to FreeBSD and Unix. I used Solaris 10 last week in
lab, and found there is a difference between them.
When Solaris is installed, press backspace will give you ^H, you'll
have to "stty erase ^H" to solve this probl
Hello,
I'm a new user to FreeBSD and Unix. I used Solaris 10 last week in
lab, and found there is a difference between them.
When Solaris is installed, press backspace will give you ^H, you'll
have to "stty erase ^H" to solve this problem. But with FreeBSD 6.1,
when first ins
o
that it does not run in vi compatibility mode.
I did this and now my backspace and delete work like I want them to. :)
I appreciate the replies.
For vim, my favorite is this:
cp /usr/local/share/vim/vim70/vimrc_example.vim ~/.vimrc
Regards,
Lars
_
doug wrote:
On Mon, 11 Jun 2007, Scott Mayo wrote:
I am not on any VI list, but thought I would post this here to see if
anyone had any ideas.
This is my first FreeBSD server, so I am still learning.
I got my backspace and delete working the shell after a few
adjustments, but they still
>
> Scott Mayo wrote:
>
> If I hit backspace it just backs up on the line until
> were input-mode
> was started during this input-mode session. If I hit
> delete then it
> capitalizes the charcter behind the cursor and throws
> me into
> command-mode.
You
Scott Mayo wrote:
If I hit backspace it just backs up on the line until
were input-mode
was started during this input-mode session. If I hit
delete then it
capitalizes the charcter behind the cursor and throws
me into
command-mode.
===
This way to get things to delete in vi seems
I am not on any VI list, but thought I would post this here to see if
anyone had any ideas.
This is my first FreeBSD server, so I am still learning.
I got my backspace and delete working the shell after a few adjustments,
but they still act odd in VI. I have checked setting with my linux
the preferences accessible from the
> >>menu.
> >>
> >>That's what I meant. Just relaying my experience because I had a similar
> >>problem recently with Suse.
> >>
> >>-Garrett
> >>
> >
> >
> > Too bad there isn&#x
re isn't some sort of web database for these sorts of
miscellany with tags like (vi backspace-failure term) that would
aide the search and solution for these type questions. This may
be one of Google's aims, but there are miles to go
gary
Someone (Chuck
Too bad there isn't some sort of web database for these sorts of
miscellany with tags like (vi backspace-failure term) that would
aide the search and solution for these type questions. This may
be one of Google's aims, but there are miles to go
gary
signment of BS/DEL to the
"backspace" key (unlike gnome-terminal, it has a manpage describing these
details ;-).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
You can set the default terminal in gnome to be xterm instead of Gnome Terminal. Gnome
then
rminal shell using the Terminal command under the menu) has
>
> gnome-terminal isn't xterm (OP isn't making that distinction either).
>
> xterm has menu settings which can change the assignment of BS/DEL to the
> "backspace" key (unlike gnome-terminal, it has
, which makes it use DEL,
FreeBSD uses BS for erase, etc).
> The terminal settings available from gnome (if you open up an xterm /
> Gnome terminal shell using the Terminal command under the menu) has
gnome-terminal isn't xterm (OP isn't making that distinction either).
xterm
Jordan Gordeev wrote:
Gary Kline wrote:
I'm not sure whether this just in Ubuntu or in the Gnome desktop
or what, but for days, when I type mail in vi in mutt, sometimes
I get a "^?" when I hit the backspace. ^H still works to back up
and correct my typos, but t
Gary Kline wrote:
I'm not sure whether this just in Ubuntu or in the Gnome desktop
or what, but for days, when I type mail in vi in mutt, sometimes
I get a "^?" when I hit the backspace. ^H still works to back up
and correct my typos, but that&#
I'm not sure whether this just in Ubuntu or in the Gnome desktop
or what, but for days, when I type mail in vi in mutt, sometimes
I get a "^?" when I hit the backspace. ^H still works to back up
and correct my typos, but that's lots mo
Constantine A. Murenin wrote:
> They map it perfectly fine as 127, it's only FreeBSD's ee(1) that has
> this problem, tcsh and others work fine.
ee does not do this on the console on my 5.4 machine, nor does it
do this in an XTerm over an ssh connection to my 4.11 machine,
therefore I would susp
On 07 Dec 2005 09:27:48 -0500, Lowell Gilbert
<[EMAIL PROTECTED]> wrote:
> "Constantine A. Murenin" <[EMAIL PROTECTED]> writes:
>
> > Hello,
> >
> > When I ssh my FreeBSD 4.8 machine and try to use ee(1), I always
> > notice that Backspace eras
"Constantine A. Murenin" <[EMAIL PROTECTED]> writes:
> Hello,
>
> When I ssh my FreeBSD 4.8 machine and try to use ee(1), I always
> notice that Backspace erases the following character, not the previous
> one. On the contrary, I've noticed that it does no
Hello,
When I ssh my FreeBSD 4.8 machine and try to use ee(1), I always
notice that Backspace erases the following character, not the previous
one. On the contrary, I've noticed that it does not do that when I
login via console.
So I decided to play with the value of $TERM.
By default, w
Hi Roger
Try M-x normal-erase-is-backspace-mode. If that works for you, then add
(normal-erase-is-backspace-mode 0) to your .emacs file. More information
is available in the Emacs manual, section: "If Fails to Delete".
Gordon
--
Gordon Farquharson
NCAR/EOL/RTF
PO Box 3000
Boulder
On Thu, Jul 14, 2005 at 11:57:51AM -0700, Ben Jencks wrote:
> Did you start the screen session from within the local/telnet/ssh/serial
> connection you're attempting to use it from? I've found that if you
> start a screen session with one keyboard/OS/keymap/method of connection,
> and attempt to us
e problems have
> plagued me through several versions though). On one system, arrows
> and backspace work as expected, but on the other, left/right arrows in
> vi cause havock (extra characters and a switch from command to insert
> mode), and backspace in Lynx, Mutt, etc., backs up but leaves
On Thu, Jul 14, 2005 at 07:57:05AM -0700, Gary W. Swearingen wrote:
> You didn't mention these (albeit unlikely) things:
> -- Different "console driver" (sc vs. vt) in kernel.
Both are the same; not using pcvt.
> -- Different "keymap" (see /etc/default/rc.conf).
Not setting key maps.
>
Doug Lee <[EMAIL PROTECTED]> writes:
> characters intact instead of clearing them. I have verified that the
> following are identical on both systems:
You didn't mention these (albeit unlikely) things:
-- Different "console driver" (sc vs. vt) in kernel.
-- Different "keymap" (see /etc/d
On Thu, Jul 14, 2005 at 04:43:32AM -0700, Glenn Dawson wrote:
> Check TERM in the environment of a shell that's inside screen. It should
> be 'screen'. If it's not, or there's no entry for screen in termcap you'll
> have exactly the problem you are seeing.
"screen" it is, and here's the /etc/t
On Thu, Jul 14, 2005 at 12:41:33PM +0100, Alex Zbyslaw wrote:
Doug Lee wrote:
> One thing to check is that both keyboards are actually producing the
> same codes for your keys. They probably are, but...
Yes they are. The truth table (or approximation thereof) also shows
that it doesn't matter
1 - 100 of 168 matches
Mail list logo
