All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Rittweiler <inkognito.anonym@uni.de>
To: Antonino Daplas <adaplas@pol.net>
Cc: James Simmons <jsimmons@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux console project <linuxconsole-dev@lists.sourceforge.net>
Subject: Re[4]: [STATUS] fbdev api.
Date: Sat, 7 Dec 2002 11:15:18 +0100	[thread overview]
Message-ID: <1702768901.20021207111518@uni.de> (raw)
In-Reply-To: <1039256356.1066.6.camel@localhost.localdomain>

Hello Antonino,

Saturday, December 7, 2002, 11:22:07 AM, you wrote:

>> >> c) instruction:          | produces:
>> >>    ======================|==================
>> >>    1. typing abc def     | $ abc def
>> >>                          |          ^ (<- cursor)
>> >>    2. going three chars  | $ abc def
>> >>       ro the left        |       ^
>> >>    3. pressing backspace | $ abcddef
>> >>                          |      ^
>> >>    4. pressing enter     | -bash: abcdef: command not found
>> >>                          |

AD> Can you try this? It should fix the problem you mentioned as well as the
AD> emacs glitch.  Also, a quick fix for character map generation failures
AD> (KDFONTOP ioctl), ie when selecting console fonts.  Finally, if fbdev
AD> supports blanking, let's use that.
AD> [..patch..]
 
Ah, good job! Now working at the shell prompt is usable again. Many
thanks for your time exposure.

AD> Tony
-- 
cheers,
 Tobias


  reply	other threads:[~2002-12-07 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 19:42 [STATUS] fbdev api Tobias Rittweiler
2002-12-06 23:55 ` Antonino Daplas
2002-12-06 22:59   ` Re[2]: " Tobias Rittweiler
2002-12-06 23:51     ` James Simmons
2002-12-07 10:22     ` Antonino Daplas
2002-12-07 10:15       ` Tobias Rittweiler [this message]
2002-12-07 19:05       ` James Simmons
2002-12-07 21:43         ` Antonino Daplas
2002-12-07  0:49   ` James Simmons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1702768901.20021207111518@uni.de \
    --to=inkognito.anonym@uni.de \
    --cc=adaplas@pol.net \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.