From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, 15109-done@debbugs.gnu.org
Subject: bug#15109: 24.3.50; doc of `x-get-selection, `selection-converter-alist', `xselect-convert-to-*'
Date: Tue, 11 Feb 2014 05:36:03 +0200 [thread overview]
Message-ID: <83eh3atj6k.fsf@gnu.org> (raw)
In-Reply-To: <dc2d04f5-4781-4ebf-845d-71a6b485255a@default>
> Date: Mon, 10 Feb 2014 13:36:12 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: larsi@gnus.org, 15109@debbugs.gnu.org
>
> > I see no reason to have selection-converter-alist documented
> > on Windows, since the functionality it encompasses is not available
> > there, and the DATA-TYPE argument to x-get-selection is completely
> > ignored on MS-Windows.
>
> In that case, why define `selection-converter-alist' at all on
> Windows? And why not rename it to `x-selection-converter-alist',
> if it is X-specific?
I explained why: because we must have identical doc strings for these
on all platforms, due to limitations of how the DOC file is built and
used.
> On the other hand, although `x-get-selection' has that prefix,
> it _is_ defined and used on Windows. Likewise, `x-set-selection'.
> Code that makes use of the secondary selection will make use of
> such functions, for instance.
>
> So maybe they should lose their `x-' prefix (or suitable unprefixed
> synonyms or wrapper functions be provided).
>
> IOW, things do not seem so cut-and-dried as you describe them.
> In the past we have renamed `x-defined-colors' to `defined-colors' etc.
> Sounds like maybe some more such cleanup is in order.
Could be. But that's a different issue. This one is done.
next prev parent reply other threads:[~2014-02-11 3:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<c143941c-9b99-42a5-b605-bdd727a83333@default>
[not found] ` <<87r47e2nkm.fsf@building.gnus.org>
[not found] ` <<af33a046-8656-4b66-ac0d-dbde3c484e02@default>
[not found] ` <<87a9dzy9hk.fsf@building.gnus.org>
[not found] ` <<601544f2-1018-4a52-9aca-6b0d815ab7d9@default>
[not found] ` <<87y51jwuco.fsf@building.gnus.org>
[not found] ` <<63fb8060-d4e0-4a2b-a506-6c758acee56d@default>
[not found] ` <<83zjlyubjn.fsf@gnu.org>
2014-02-10 21:36 ` bug#15109: 24.3.50; doc of `x-get-selection, `selection-converter-alist', `xselect-convert-to-*' Drew Adams
2014-02-11 3:36 ` Eli Zaretskii [this message]
2014-02-11 3:50 ` Stefan Monnier
2013-08-16 6:49 Drew Adams
2014-02-08 5:14 ` Lars Ingebrigtsen
2014-02-10 0:27 ` Drew Adams
2014-02-10 2:41 ` Lars Ingebrigtsen
2014-02-10 2:47 ` Drew Adams
2014-02-10 2:49 ` Drew Adams
2014-02-10 2:54 ` Lars Ingebrigtsen
2014-02-10 3:09 ` Drew Adams
2014-02-10 17:23 ` 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=83eh3atj6k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15109-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.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.