From: Seiichi Nakashima <nakasima@kumin.ne.jp>
To: linux-fbdev-devel@lists.sourceforge.net.
Subject: VESA VGA Graphic console has error to use emacs
Date: Tue, 13 Aug 2002 07:57:32 +0900 [thread overview]
Message-ID: <200208122257.AA00113@prism.kumin.ne.jp> (raw)
Hi.
I found VESA VGA Graphic console at linux-2.5.31 again.
and I was adviced by Petr Vandrovec that forward to linux-fbdev-devel@lists.sourceforge.net
=====
>I use linux-2.5.30 with VESA VGA Graphic console at slackware-8.1 based environment.
>when I use emacs( 21.2 ), these situation occured. (I used to boot up with vga=771)
>
>(1) # emacs /tmp/test
> I type a line ( /sbin/ifconfig lo 127.0.0.1 ), and save file.
>
>(2) # emacs /tmp/test
> a line ( /sbin/ifconfig lo 127.0.0.1 ) displayed in emacs frame.
>
>(3) I wand to insert few spaces between /sbin/ifconfig and lo.
> when I type a space, then a line change to a line ( /sbin/ifconfig oo 127.0.0.1 ).
> I could not edit a line as I want to edit.
> this situation display only. when I save file and re-read file, results were fine.
>
>(4) I boot up PC ( erase VGA option ), I checked this test, everything OK.
>
>I checked a same test at linux-2.5.26,28,30 and got a same result.
>I checked at linux-2.4.19, it is OK( everything work fine with vga=771 ).
>I thinked VESA VGA Graphic console has bug to display in emacs frame.
>
>Before VESA VGA Graphic console occured kernel panic at linux-2.5.14,15.
>from linux-2.5.16 VESA VGA Graphic console compile and work fine,
>but Pengin Image did not display at boot up time. is it OK?
--------------------------------
Seiichi Nakashima
Email nakasima@kumin.ne.jp
--------------------------------
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
reply other threads:[~2002-08-12 22:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200208122257.AA00113@prism.kumin.ne.jp \
--to=nakasima@kumin.ne.jp \
--cc=linux-fbdev-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).