unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Nathan Trapuzzano <nbtrap@nbtrap.com>
Cc: 16415@debbugs.gnu.org
Subject: bug#16415: 24.3.50; Handle contiguous links correctly in shr [PATCH]
Date: Thu, 30 Jan 2014 18:09:56 -0800	[thread overview]
Message-ID: <87y51wyk97.fsf@building.gnus.org> (raw)
In-Reply-To: <87iotrfbi6.fsf@nbtrap.com> (Nathan Trapuzzano's message of "Fri,  10 Jan 2014 22:22:41 -0500")

Nathan Trapuzzano <nbtrap@nbtrap.com> writes:

> `shr-next-link' and `shr-previous-link' currently skip over links that
> are contiguous with the current link.  The attached patch addressed this
> problem.
>
> When I say "contiguous", I'm talking in terms of Emacs "positions"--not
> in terms of HTML.
>
> P.S. I'm still waiting for my boss to return the copyright disclaimer
> form to me.  Hopefully this change is minor enough...

The patch looks good, but it's big enough that the FSF needs a copyright
assignment, I think.  Do you have one of those on file?

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  parent reply	other threads:[~2014-01-31  2:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11  3:22 bug#16415: 24.3.50; Handle contiguous links correctly in shr [PATCH] Nathan Trapuzzano
2014-01-11 12:50 ` Nathan Trapuzzano
2014-01-20 13:20   ` Nathan Trapuzzano
2014-01-31  2:09 ` Lars Ingebrigtsen [this message]
2014-01-31 16:06   ` nbtrap
2014-11-13 18:42     ` Lars Magne Ingebrigtsen
2015-12-25 17:37       ` Lars Ingebrigtsen
2015-12-26 11:10         ` bug#16415: 24.3.50; Handle contiguous links correctly in shr Ivan Shmakov
2015-12-26 12:12           ` Eli Zaretskii
2015-12-26 12:40             ` Ivan Shmakov
2015-12-26 13:02               ` Eli Zaretskii
2015-12-26 13:07                 ` Ivan Shmakov
2015-12-26 13:09                 ` Lars Ingebrigtsen
2015-12-28 21:21           ` Lars Ingebrigtsen

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=87y51wyk97.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --cc=16415@debbugs.gnu.org \
    --cc=nbtrap@nbtrap.com \
    /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).