unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: lennart.borgman.073@student.lu.se, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Saving when the coding system can't code all buffer characters
Date: Wed, 27 Dec 2006 10:28:13 +0200	[thread overview]
Message-ID: <ur6ul215u.fsf@gnu.org> (raw)
In-Reply-To: <E1GzNlb-00062s-P4@etlken.m17n.org> (message from Kenichi Handa on Wed, 27 Dec 2006 10:39:39 +0900)

> From: Kenichi Handa <handa@m17n.org>
> Date: Wed, 27 Dec 2006 10:39:39 +0900
> Cc: lennart.borgman.073@student.lu.se, emacs-devel@gnu.org
> 
> > I suggested people make it show all the relevant information _at the
> > outset_.  Would you like to try implementing that, please?
> 
> Even if we put all the relevant information in *Warning*
> buffer, as the window height is limited, a user have to
> switch to *Warning* buffer and scroll up/down to see all of
> them.

We could make SPC scroll *Warning*, as we do with *Help* buffers.

  parent reply	other threads:[~2006-12-27  8:28 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21 22:40 Saving when the coding system can't code all buffer characters Lennart Borgman
2006-12-22 10:50 ` Eli Zaretskii
2006-12-22 21:03 ` Richard Stallman
2006-12-23 12:09   ` Kenichi Handa
2006-12-24  1:35     ` Richard Stallman
2006-12-25  6:00       ` Kenichi Handa
2006-12-26  2:25         ` Richard Stallman
2006-12-27  1:39           ` Kenichi Handa
2006-12-27  2:59             ` Lennart Borgman (gmail)
2006-12-27  5:13               ` Kenichi Handa
2006-12-27 13:27                 ` Eli Zaretskii
2006-12-27 21:16                   ` Richard Stallman
2006-12-28  2:09                   ` Kenichi Handa
2006-12-27  8:28             ` Eli Zaretskii [this message]
2006-12-27 11:06               ` Kenichi Handa
2006-12-27 12:20                 ` Eli Zaretskii
2006-12-27 12:37                   ` Lennart Borgman (gmail)
2006-12-27 14:17                     ` Eli Zaretskii
2006-12-28  0:31                   ` Kenichi Handa
2006-12-27 21:16             ` Richard Stallman
2006-12-28  1:32               ` Kenichi Handa
2006-12-28  4:20               ` Eli Zaretskii
2006-12-29 15:44                 ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2006-12-22 11:15 LENNART BORGMAN
2006-12-22 11:50 ` Eli Zaretskii
2006-12-22 15:48   ` David Kastrup
2006-12-22 16:23     ` Lennart Borgman
2006-12-23  7:31       ` David Kastrup
2006-12-31 14:36       ` Sascha Wilde
2006-12-31 16:04         ` Lennart Borgman
2006-12-31 19:27           ` Aidan Kehoe
2007-01-09  7:23         ` Kenichi Handa
2006-12-22 17:35   ` Lennart Borgman
2006-12-23 20:14   ` Richard Stallman
2006-12-23 20:41     ` Lennart Borgman
2006-12-24 17:09       ` Richard Stallman

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=ur6ul215u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman.073@student.lu.se \
    --cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).