From: RCDRUN <support1-ZohPw8X7yHTQT0dZR+AlfA@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: How I copy HTML from browser to markdown by using pandoc
Date: Fri, 5 May 2017 13:00:11 +0300 [thread overview]
Message-ID: <20170505100011.GA11734@protected.rcdrun.com> (raw)
In-Reply-To: <bb322584-959f-4fbe-aceb-1d87128487dd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
On Fri, May 05, 2017 at 02:53:21AM -0700, Kolen Cheung wrote:
> you might try http://heckyesmarkdown.com
Oh, you want me to spend time by copy pasting URLs into some website?
:-)
My short article is about HTML snippets, not the full pages. Otherwise
it becomes tiresom to edit the Markdown.
Imagine you have 200 pages, like I collected yesterday, than all the
process of
1. copy URL
2. paste URL
3. copy markdown
4. open editor
5. paste markdown
6. edit markdown as it is whole page
7. save file
is much longer than
1. copy HTML
2. Press key and file is saved automatically
2. rarely edit anything
Jean
next prev parent reply other threads:[~2017-05-05 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 14:32 support1-ZohPw8X7yHTQT0dZR+AlfA
[not found] ` <20170504143246.GB23510-vvHXCvOI15V+RnA8QueWCFaTQe2KTcn/@public.gmane.org>
2017-05-05 9:53 ` Kolen Cheung
[not found] ` <bb322584-959f-4fbe-aceb-1d87128487dd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-05-05 10:00 ` RCDRUN [this message]
[not found] ` <20170505100011.GA11734-vvHXCvOI15V+RnA8QueWCFaTQe2KTcn/@public.gmane.org>
2017-05-06 0:55 ` Kolen Cheung
[not found] ` <58c1d809-a2c3-4a1e-a053-6b1f55da4576-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-05-06 0:59 ` Kolen Cheung
[not found] ` <5977ca6e-4cda-4548-a82a-c5fdabaa9368-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-05-06 8:03 ` support1-ZohPw8X7yHTQT0dZR+AlfA
2017-05-06 8:01 ` support1-ZohPw8X7yHTQT0dZR+AlfA
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=20170505100011.GA11734@protected.rcdrun.com \
--to=support1-zohpw8x7yhtqt0dzr+alfa@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).