all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Gramiak <agrambot@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Removing assumption of unsigned long pixel values for colours
Date: Mon, 06 May 2019 13:49:30 -0600	[thread overview]
Message-ID: <87pnovics5.fsf@gmail.com> (raw)
In-Reply-To: <83a7fzjwdz.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 06 May 2019 21:00:40 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Once again: why?

A table lookup would require memory allocation that could be easily
avoided if the integral representation that Emacs uses for colours was
at least 64-bit instead of 32-bit.

> And what table look up do you need, when you originally said that a
> conversion would do?  What am I missing?

I brought up the table lookup as an alternative to the converted
embedding scheme if you weren't okay with widening the integral
representation. Otherwise the embedding could lose precision as
mentioned previously.

> Btw, I think this discussion basically puts the cart before the horse,
> so to speak.  You say you are developing a new back-end, which might
> need these changes, but we never saw that back-end and didn't yet
> decide it's a useful addition to Emacs.  IMO, this is the wrong order
> of discussing this stuff.  let's first see the feature itself, discuss
> its implementation and integration with Emacs, and only after that
> talk about any necessary changes in the infrastructure.  That way, all
> the sides of the discussion will know what's at stake, and the
> discussion becomes more concrete.
>
> OK?

Sure, though I don't know what relevant information is missing; the goal
of this thread was to determine if a certain change is suitable
_assuming_ that such a backend is submitted with the change, and that
the backend needs it (or rather finds it sufficiently useful). I just
wanted to avoid having to implement the union scheme fully and having to
revert it upon review. It turns out that it was good to post this, since
I was assured that using the integral representation is good enough.

I can just restrict the colours to 8bpc in the meantime.



  reply	other threads:[~2019-05-06 19:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-04 18:08 Removing assumption of unsigned long pixel values for colours Alex Gramiak
2019-05-04 18:39 ` Eli Zaretskii
2019-05-04 23:04   ` Alex Gramiak
2019-05-05 16:14     ` Eli Zaretskii
2019-05-05 19:35       ` Alex Gramiak
2019-05-06  2:45         ` Eli Zaretskii
2019-05-06 14:13           ` Daniel Pittman
2019-05-06 16:11             ` Alex Gramiak
2019-05-06 16:51               ` Stefan Monnier
2019-05-06 20:03                 ` Alex Gramiak
2019-05-06 15:11           ` Alex Gramiak
2019-05-06 15:45             ` Eli Zaretskii
2019-05-06 16:29               ` Alex Gramiak
2019-05-06 16:54                 ` Eli Zaretskii
2019-05-06 17:14                   ` Alex Gramiak
2019-05-06 17:39                     ` Eli Zaretskii
2019-05-06 18:00                       ` Eli Zaretskii
2019-05-06 19:49                         ` Alex Gramiak [this message]
2019-05-07  2:29                           ` Eli Zaretskii
2019-05-06  8:12     ` Alan Third
2019-05-06  9:18       ` mituharu
2019-05-06 15:06       ` Eli Zaretskii

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=87pnovics5.fsf@gmail.com \
    --to=agrambot@gmail.com \
    --cc=eliz@gnu.org \
    --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.