unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: joakim@verona.se
Cc: emacs-devel@gnu.org
Subject: Re: Initial documentation for xwidgets
Date: Sat, 13 Feb 2016 11:09:31 +0200	[thread overview]
Message-ID: <83ziv55644.fsf@gnu.org> (raw)
In-Reply-To: <m3bn7ld33c.fsf@exodia.verona.se> (joakim@verona.se)

> From: joakim@verona.se
> Cc: emacs-devel@gnu.org
> Date: Fri, 12 Feb 2016 22:35:19 +0100
> 
> > Are you sure?  I cannot imagine I was that lucky.  There are some
> > functions I didn't document, some of them in xwidget.c, others in
> > xwidget.el -- did I decide correctly which ones should be documented
> > and which shouldn't?
> 
> I think you did a better job than I would have done. But let me have an
> extra look.

Thanks.

> >> - This fixme, I dont really have a good answer.
> >>   @c FIXME: What else can a URI specify in this context?
> >> The uri is just any ury webkit accepts, which isnt a very helpful
> >>   explanation of course.
> >
> > Examples could help.  Can you provide examples of URIs that are
> > neither URLs nor file names?

Please also try to give a few examples, I have a bad feeling about
what I wrote in that part.

> >> I guess people might have started tinkering with xwidget-osr.
> >> 
> >> What do you think, should I change this, or does it not matter?
> >
> > We can still change it, it's not too late.
> 
> Ok, I will change it then.
> 
> BTW, when will it be too late to make these kind of changes?

I don't know, it depends on the changes.



      parent reply	other threads:[~2016-02-13  9:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30  8:13 Initial documentation for xwidgets Eli Zaretskii
2016-02-12 21:08 ` joakim
2016-02-12 21:20   ` Paul Eggert
2016-02-12 21:25   ` Eli Zaretskii
2016-02-12 21:35     ` joakim
2016-02-12 21:40       ` joakim
2016-02-12 21:55         ` Paul Eggert
2016-02-13  9:09           ` Eli Zaretskii
2016-02-13  9:09       ` Eli Zaretskii [this message]

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=83ziv55644.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    /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).