unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: epameinondas@gmx.de
Cc: emacs-devel@gnu.org
Subject: Re: [patch] XPM in gamegrid.el
Date: Fri, 05 Jul 2002 10:08:25 +0200	[thread overview]
Message-ID: <m3adp6ppfq.fsf@ID-87814.user.dfncis.de> (raw)
In-Reply-To: <200207041824.g64IO3906414@aztec.santafe.edu> (Richard Stallman's message of "Thu, 4 Jul 2002 12:24:03 -0600 (MDT)")

Richard Stallman <rms@gnu.org> writes:
[...]
> I see.  Maybe we should have a way for the buffer to choose
> a default face.
>
>     To have true buffer local faces would be nice.
>
> Buffer local *face definitions* would be rather hairy.  Do we need
> them?  It could be a lot easier to have a variable whose value
> specifies the name of the default face, and then you could give
> that variable a buffer-local value.  Is it really useful to
> give the same face name various buffer-local definitions?

To have a variable would be enough for most purposes I can think
of. It surely is enough for gamegrid.

Another thing, BTW, that should be buffer-local rather than frame
local is the frame parameter `cursor-type'. I am mainly thinking of
the ability to turn the cursor off via 

(modify-frame-parameters nil '((cursor-type . nil)))

gamegrid.el provides a function that turns the cursor off in XEmacs. I
have not enabled this, of course, because it should only apply to the
game buffer.

[Other cases where I, as a User, would like to turn the cursor off are
dired or the *Group* and *Article* buffers in Gnus. I'd prefer to use
the line highlighting facility provided by `hl-line-mode' to select
things.]


    -- Oliver

-- 
Oliver Scholz               17 Messidor an 210 de la Révolution
Taunusstr. 25               Liberté, Egalité, Fraternité!
60329 Frankfurt a. M.
Tel. (069) 97 40 99 42

  parent reply	other threads:[~2002-07-05  8:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-01 14:01 [patch] XPM in gamegrid.el Oliver Scholz
2002-07-02 19:46 ` Richard Stallman
2002-07-03 12:39   ` Oliver Scholz
2002-07-04 18:24     ` Richard Stallman
2002-07-04 19:10       ` Stefan Monnier
2002-07-04 23:29         ` Miles Bader
2002-07-05 10:59         ` Per Abrahamsen
2002-07-06 10:01           ` Richard Stallman
2002-07-05 22:05         ` Richard Stallman
2002-07-05 23:30           ` Miles Bader
2002-07-06  3:49             ` Miles Bader
2002-07-06 23:32               ` Richard Stallman
2002-07-06 23:31             ` Richard Stallman
2002-07-08  1:28               ` Miles Bader
2002-07-09  1:44                 ` Richard Stallman
2002-07-09  3:36                   ` Miles Bader
2002-07-08  1:34               ` Miles Bader
2002-07-05  8:08       ` epameinondas [this message]
2002-07-05  8:50         ` John Paul Wallington
2002-07-05  8:51         ` Miles Bader
2002-07-05 11:32           ` Oliver Scholz
2002-07-04 18:24     ` 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=m3adp6ppfq.fsf@ID-87814.user.dfncis.de \
    --to=epameinondas@gmx.de \
    --cc=emacs-devel@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).