all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: sindikat <sindikat@mail36.net>
Cc: 10268-done@debbugs.gnu.org
Subject: bug#10268: Internal links ?
Date: Tue, 1 Sep 2020 18:18:38 -0700	[thread overview]
Message-ID: <CADwFkmndFowJEm_0ddr_2wU4FphcSYr8XaGETbxo8Vrb4qCQeA@mail.gmail.com> (raw)
In-Reply-To: <20111210213320.28189.qmail@rage.so36.net> (sindikat@mail36.net's message of "Sat, 10 Dec 2011 22:33:20 +0100")

"sindikat" <sindikat@mail36.net> writes:

> Package: emacs-xwidgets Internal links work everywhere, where i checked, but
> possible the code on them is unfinished. Internal links definitely work on
> Emacswiki and Wikipedia Quote:
>>>>ive added a rudimentary function "xwidget-webkit-show-named-element" for this
>>>Running the function itself with named element id works, but clicking on links to section - doesn't. Also, clicking on section links eats much CPU (checked on wikipedia articles)
>>i made some notes in readme.xwidget. relative links actually work now for simple sites like emacswiki anyway

(That was 8 years ago.)

I have no idea if that needs more work or not.  To find out, someone
needs to test it and then possibly point to some concrete issue or
improvement that would need to be made.  We can only hope that if and
when users test this feature and encounter problems, they will report
it as bugs or feature requests.

Unfortunately, I see nothing actionable here beyond that, so I'm
closing this bug report now.

If you believe that this conclusion is incorrect, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.

Thanks.

Best regards,
Stefan Kangas





           reply	other threads:[~2020-09-02  1:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20111210213320.28189.qmail@rage.so36.net>]

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=CADwFkmndFowJEm_0ddr_2wU4FphcSYr8XaGETbxo8Vrb4qCQeA@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=10268-done@debbugs.gnu.org \
    --cc=sindikat@mail36.net \
    /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.