From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: storm@cua.dk
Subject: Re: Be prepared for "code clean-up" in CVS head
Date: Wed, 5 Mar 2003 15:49:58 -0600 (CST) [thread overview]
Message-ID: <200303052149.PAA10133@eel.dms.auburn.edu> (raw)
In-Reply-To: <E18qfnW-00086r-00@fencepost.gnu.org> (message from Richard Stallman on Wed, 05 Mar 2003 15:47:30 -0500)
Richard Stallman wrote:
About code cleanup, how about removing the pure X (i.e. not Xt, not GTK)
parts? That would not reduce the duplication but would remove a lot
of #ifdef:s. Is there a configuration that has X but not Xt?
It's not clear that the only reason for the non-toolkit version is to
support configurations that don't have Xt. (I don't think there ever
were any such.) There might be users who prefer the non-toolkit
version.
However, they are probably few, and maybe it is ok to delete the
non-toolkit code. I am not saying I am sure we need to keep it, only
that we shouldn't look at it purely as a question of whether Xt is
available.
The main reason I know of to want non-toolkit scroll-bars (but just
scroll bars, i.e. configuring using
./configure --without-toolkit-scroll-bars) is to be able to split
windows using C-mouse-2. It is unclear to me whether this would be
affected by the proposed changes. (If not, then of course this remark
is irrelevant.)
Sincerely,
Luc.
next prev parent reply other threads:[~2003-03-05 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 16:11 Be prepared for "code clean-up" in CVS head Kim F. Storm
2003-03-04 16:06 ` Juanma Barranquero
2003-03-04 17:23 ` Jan D.
2003-03-05 20:47 ` Richard Stallman
2003-03-05 21:49 ` Luc Teirlinck [this message]
2003-03-07 19:41 ` Richard Stallman
2003-03-06 4:27 ` Eli Zaretskii
2003-03-17 5:49 ` chad Brown
2003-03-10 18:32 ` Stefan Monnier
2003-03-05 20:47 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200303052149.PAA10133@eel.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=storm@cua.dk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.