From: "Nicholas Savage" <firstname.lastname@example.org>
To: "Emanuel Berg via General discussions about Org-mode."
Subject: Re: bug#47088: org-w3m: handle w3m-image link information
Date: Sat, 08 May 2021 07:35:35 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
I have applied it now as commit 5d2ccdae7f in master. Thank you, Boruch!
On Sat, May 8, 2021, at 03:44, Bastien wrote:
> Hi Nick,
> Nick Savage <firstname.lastname@example.org> writes:
> > I haven't opened up the code yet to take a look, but I likely will
> > take a crack at some of these items in the future as low-hanging fruit
> > refactoring project.
> Please feel free to go ahead and enhance ol-w3m.el in Org's repo with
> the patches that Boruch kindly provided---and other enhancements that
> you would find useful.
next prev parent reply other threads:[~2021-05-08 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210312062614.usandeuwplmn7fu3@E15-2016.optimum.net>
2021-05-05 8:16 ` Bastien
2021-05-06 22:05 ` Boruch Baum
2021-05-06 23:56 ` Nick Savage
2021-05-08 7:44 ` Bastien
2021-05-08 11:35 ` Nicholas Savage [this message]
2021-05-09 6:50 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).