unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Lute Kamstra <Lute.Kamstra@cwi.nl>
Subject: Re: Emacs 21 and M-x term
Date: Thu, 04 Sep 2003 18:39:08 +0200	[thread overview]
Message-ID: <sgdfzjcpkyb.fsf@occarina.pna.cwi.nl> (raw)
In-Reply-To: <mailman.135.1062682802.18171.help-gnu-emacs@gnu.org> (Mark Plaksin's message of "04 Sep 2003 09:39:47 -0400")

Mark Plaksin <happy@usg.edu> writes:

> Lute Kamstra <Lute.Kamstra@cwi.nl> writes:
>
>> We just fixed the problem of things not being properly aligned in
>> CVS Emacs.  I do not recognize your problem of term not using more
>> than half of the window.  Could you check out the latest CVS and
>> see if the problem still exist?  If so, could you read the bug
>> reporting section of the Emacs manual (C-h i d m Emacs RET m Bugs
>> RET) and write a bug report to emacs-pretest-bug@gnu.org?
>
> My main problem seems to have been using Debian unstable.  With
> Debian woody and CVS Emacs, it's much better.  Almost all of the
> rest of my problems went away when I compiled eterm.ti on all of the
> hosts and set TERM to eterm.

So, which problems remain?

> In the past CVS Emacs has behaved the same in both woody and
> unstable.  With CVS Emacs in unstable I still have the "only uses
> half the screen" problem.  There are other problems as well even
> with TERM set to eterm.
>
> I'm guessing that you don't want bug reports about Debian unstable
> since it is unstable.

It is possible that there are bugs in Emacs that show up on Debian
unstable and not on Debian stable.  If you are reasonably sure that
the problems you are experiencing are due to a bug in Emacs, we very
much like to hear from you.  (Take a look a the Emacs Manual for some
guidelines with respect to bug reporting.)

> Do you have any clues about where I might look for the solution on
> my own?

I don't know much about terminals, but maybe you can try to debug it?
The Emacs Lisp Reference Manual (included with CVS Emacs) has a
chapter on debugging lisp.  You could use the source level debugger to
see what goes wrong on Debian unstable.  (Additionally, you can use
the debugger on Debian stable to see how things should go.)

  Lute.

-- 
(spook) => "cryptanalysis AVN csim"
(insert-file-contents "~/.signature") => (error "`~/.signature' too rude")

  parent reply	other threads:[~2003-09-04 16:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1385.1062441899.29551.help-gnu-emacs@gnu.org>
2003-09-01 19:10 ` Emacs 21 and M-x term Lute Kamstra
2003-09-04 13:39   ` Mark Plaksin
     [not found]   ` <mailman.135.1062682802.18171.help-gnu-emacs@gnu.org>
2003-09-04 16:39     ` Lute Kamstra [this message]
2003-09-09  0:17       ` Mark Plaksin
     [not found]       ` <mailman.36.1063066672.21628.help-gnu-emacs@gnu.org>
2003-09-09 10:18         ` Lute Kamstra
2003-09-10  1:39           ` Mark Plaksin
     [not found]           ` <mailman.101.1063158543.21628.help-gnu-emacs@gnu.org>
2003-09-10  8:44             ` Lute Kamstra
2003-09-01 16:32 Mark Plaksin

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=sgdfzjcpkyb.fsf@occarina.pna.cwi.nl \
    --to=lute.kamstra@cwi.nl \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).