all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: charles@aurox.ch, emacs-devel@gnu.org
Subject: Re: Change to NS drawing routines
Date: Mon, 13 Aug 2018 22:10:41 +0300	[thread overview]
Message-ID: <83in4ejd5a.fsf@gnu.org> (raw)
In-Reply-To: <20180813184659.GA2258@breton.holly.idiocy.org> (message from Alan Third on Mon, 13 Aug 2018 19:46:59 +0100)

> Date: Mon, 13 Aug 2018 19:46:59 +0100
> From: Alan Third <alan@idiocy.org>
> Cc: emacs-devel@gnu.org
> 
> Going through the previous email discussions, linked in the thread
> above, Eli made it clear that he sees using the expose functions to
> draw, when it’s not an expose event, as being incorrect.
> 
> i.e. this:
> 
> > > Again, invalidating an area to let the "expose" handler draw
> > > afterwards is a very standard, primary, canonical, and sometimes
> > > only way of drawing nowadays. (If you call it is an abuse or
> > > trick, you'll be laughed.)
> > 
> > You can laugh, if you want, but I still think it's abuse, and won't
> > be convinced by being laughed at.
> 
> from http://lists.gnu.org/archive/html/emacs-devel/2013-04/msg00435.html
> 
> I can understand the argument to an extent, but I don’t have another
> solution.

We could discuss this again, perhaps the details have changed, or we
might be able o find some compromise everybody can live with.

For starters, what changes, if any, would you need to make in the
glyph matrices, and why?



  reply	other threads:[~2018-08-13 19:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-11 14:06 Change to NS drawing routines Alan Third
2018-08-12 10:47 ` Charles A. Roelli
2018-08-13 18:46   ` Alan Third
2018-08-13 19:10     ` Eli Zaretskii [this message]
2018-08-13 19:36       ` Alan Third
2018-08-14 14:50         ` Eli Zaretskii
2018-08-15 20:43           ` Alan Third
2018-08-15 19:20     ` Charles A. Roelli
2018-08-15 20:42       ` Alan Third
2018-08-13  8:24 ` Nick Helm
2018-08-13  9:15 ` Van L

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=83in4ejd5a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=alan@idiocy.org \
    --cc=charles@aurox.ch \
    --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 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.