From: Mike McCarty <Mike.McCarty@sbcglobal.net>
To: linux-msdos@vger.kernel.org
Subject: Re: Setting up new dosemu 1.3.3
Date: Wed, 12 Apr 2006 02:12:46 -0500 [thread overview]
Message-ID: <443CA86E.8050500@sbcglobal.net> (raw)
In-Reply-To: <443C29DB.3000504@mindspring.com>
Larry Alkoff wrote:
> Mike McCarty wrote:
>
>>
>> I have the same problem, along with the lower contrast.
>>
>> Here's what I do, using the GNOME descktop manager:
>>
>> (1) Start a text window
>> (2) $ xterm -pc -fg white -bg black -geometry 80x25
>> (3) When the window opens, in the text area...
>> CTRL-RightMouseButton->Font->HUGE
>>
>> You may prefer to switch the bg/fg colors, but anyway this gives a
>> nice large font with intense contrasty colors.
>>
>> HTH
>>
>> Mike
>
>
>
> Mike are you using dosemu 1.2.2?
1.3.2.0
> The behavior has changed.
>
> I used to use the same method before changing to 1.3.3 with either the
> HUGE font or selecting a font in .dosemurc.
Yes, I select the HUGE font.
> The latest version 1.3.3 does not take on the geometry and font from the
> xterm - it sets up it's own window.
Hmm. Are you using dosemu or are you using xdosemu? I don't use
xdosemu, since its behavior is as you describe. But if I start
an xterm -pc -geometry 80x25 & and then set the font to HUGE
before starting dosemu, it works for me.
> The 80x25 seems to be a default - don't know it it can be changed or not
> but 80x25 works well for me. The font selected in .dosemurc determines
> the actual window size.
I don't have a .dosemurc anywhere in my $HOME tree.
> I'm currently using the biggest font I can find:
> $_X_font = "vga12x30" # The biggest 11" wide x 8.5"high on 19"
> 1280x1024 screen.
Well, if it works for you, then I guess you are ok. But I find that
starting my own xterm, setting font size, and then using dosemu
works for me. I don't use xdosemu for the reasons you give.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
next prev parent reply other threads:[~2006-04-12 7:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 17:05 Setting up new dosemu 1.3.3 Larry Alkoff
2006-04-10 20:25 ` Claudia Neumann
2006-04-10 21:15 ` Larry Alkoff
2006-04-11 9:11 ` Bart Oldeman
2006-04-11 17:20 ` Mike McCarty
2006-04-11 22:12 ` Larry Alkoff
2006-04-12 1:34 ` Karl.
2006-04-12 2:02 ` Larry Alkoff
2006-04-12 2:18 ` Karl.
2006-04-12 2:40 ` jegunn
2006-04-12 5:08 ` Larry Alkoff
2006-04-12 7:12 ` Mike McCarty [this message]
2006-04-12 14:24 ` Larry Alkoff
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=443CA86E.8050500@sbcglobal.net \
--to=mike.mccarty@sbcglobal.net \
--cc=linux-msdos@vger.kernel.org \
/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