emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ypo <ypuntot@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: bugs@gnu.support, Org-mode <emacs-orgmode@gnu.org>
Subject: Re: idea for capture anywhere in x
Date: Wed, 12 Oct 2022 12:43:04 +0200	[thread overview]
Message-ID: <86876850-b1cd-e495-60c7-b091dbebdd9e@gmail.com> (raw)
In-Reply-To: <8735btidvh.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 758 bytes --]

Thanks, Ihor.

But I was referring to 2 possible workflows (not sure if org-protocol 
would be the answer).

The first workflow would consist in emphasizing the web page permanently:


1. Open in ~eww~ the web page.

2. Emphasize with org-mode: highlight the text of the web page.

3. In the future, when opening again the web page, the highlights should 
appear.


I don't know what would be the best way to do it. The only way I know 
similar to that, is using "org-web-tools-insert-web-page-as-entry".

Best regards



El 12/10/2022 a las 11:34, Ihor Radchenko escribió:
> Ypo<ypuntot@gmail.com>  writes:
>
>> What if:
>> 1. It were easy and immediate to open in ~eww~ any web page that we are
>> reading in "x".
> Check out org-protocol.el commentary.
>

[-- Attachment #2: Type: text/html, Size: 2247 bytes --]

  reply	other threads:[~2022-10-12 10:47 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-09 20:15 idea for capture anywhere in x Ypo
2022-10-12  9:34 ` Ihor Radchenko
2022-10-12 10:43   ` Ypo [this message]
2022-10-12 11:37     ` Ihor Radchenko
2022-10-12 16:55       ` Jean Louis
2022-10-12 23:14         ` Ihor Radchenko
2022-10-13 11:16           ` Jean Louis
2022-10-12 14:22     ` Juan Manuel Macías
     [not found] <mailman.51.1599580808.12104.emacs-orgmode@gnu.org>
2020-09-08 23:15 ` No Wayman
2020-09-13 20:29   ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2020-09-08  4:22 Samuel Wales
2020-09-08  5:01 ` Tim Cross
2020-09-08  5:05   ` Samuel Wales
2020-09-08  5:21     ` Tim Cross
2020-09-08  7:18       ` Maxim Nikulin
2020-09-08  8:03         ` Diego Zamboni
2020-09-08 16:08           ` Maxim Nikulin
2020-09-08  5:39     ` Maxim Nikulin
2020-09-08 22:40       ` Samuel Wales
2020-09-09  4:52         ` Maxim Nikulin
2020-09-10 14:23           ` Maxim Nikulin
2020-09-12  8:48             ` Nick Econopouly
2022-06-10  2:35               ` Samuel Wales
2022-06-10  9:59                 ` Charles Philip Chan
2022-06-11  4:11                 ` Ihor Radchenko
2022-06-13  7:46                 ` Max Nikulin
2022-06-13  9:10                 ` Michal Politowski
2022-06-13 10:04                   ` Max Nikulin
2022-06-13 14:02                     ` Michal Politowski
2022-10-12  1:09                       ` Samuel Wales
2022-10-09 14:47                 ` Jean Louis
2022-10-09 16:40                   ` Max Nikulin
2022-10-09 17:08                     ` Jean Louis
2022-10-10 17:16                       ` Max Nikulin
2022-10-10 22:06                         ` Jean Louis
2022-10-11  9:11                           ` Juan Manuel Macías
2022-10-12  1:09                             ` Samuel Wales
2022-10-15  3:40                               ` Max Nikulin
2022-10-26  4:40                                 ` Samuel Wales
2022-10-26  4:58                                   ` Ihor Radchenko
2022-10-26  5:05                                     ` Samuel Wales
2022-10-12 17:16                           ` Max Nikulin
2022-10-12 20:06                             ` Jean Louis
2020-09-09  8:40     ` Russell Adams
2020-09-09 21:11       ` Samuel Wales
2020-09-09  1:07 ` Ihor Radchenko

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86876850-b1cd-e495-60c7-b091dbebdd9e@gmail.com \
    --to=ypuntot@gmail.com \
    --cc=bugs@gnu.support \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.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/org-mode.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).