unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 15109@debbugs.gnu.org
Subject: bug#15109: 24.3.50; doc of `x-get-selection, `selection-converter-alist', `xselect-convert-to-*'
Date: Sun, 9 Feb 2014 19:09:33 -0800 (PST)	[thread overview]
Message-ID: <63fb8060-d4e0-4a2b-a506-6c758acee56d@default> (raw)
In-Reply-To: <87y51jwuco.fsf@building.gnus.org>

> > I do not see anything for `C-h v' in a build from 2 days ago,
> > but it is possible that it was added since then.
> 
> bzr seems to say that it's been there since at least 2001...

I see.  Then maybe it is a Windows problem somehow.  Perhaps
Eli can help.  He can hopefully confirm that C-h v shows no doc.

> > Or maybe, as you suggest, it is a MS Windows problem.
> 
> It's pretty odd.  Could it have something to do with these variables
> being X-related and...  somehow... stripped of their doc strings
> under Windows?
> 
> I think that sounds wildly unlikely, but I'm just guessing here.

We'll get there eventually.  When this is all said and done,
what about adding a comment in select.el next to the setq that
initializes the variable, saying that the doc string is defined
in select.c?  And maybe saying _why_ it is done there and not
in Lisp?  I would think that such a dependence would be pointed
out somewhere.  A comment there seems appropriate.





  reply	other threads:[~2014-02-10  3:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16  6:49 bug#15109: 24.3.50; doc of `x-get-selection, `selection-converter-alist', `xselect-convert-to-*' 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 [this message]
2014-02-10 17:23             ` Eli Zaretskii
     [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               ` Drew Adams
2014-02-11  3:36                 ` Eli Zaretskii
2014-02-11  3:50                 ` Stefan Monnier

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=63fb8060-d4e0-4a2b-a506-6c758acee56d@default \
    --to=drew.adams@oracle.com \
    --cc=15109@debbugs.gnu.org \
    --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 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).