From: Cassio Koshikumo <ckoshikumo@gmail.com>
To: Daniel Fleischer <danflscr@gmail.com>
Cc: emacs-orgmode@gnu.org, Timothy <tecosaur@gmail.com>
Subject: Re: [BUG] Creating sparse tree with regexp property matches
Date: Tue, 31 Aug 2021 09:41:16 -0300 [thread overview]
Message-ID: <CAJP-4jMMtHb93mFyZo4GGsibZcOuE-dPKsvdg16wm-MKWp6UFQ@mail.gmail.com> (raw)
In-Reply-To: <m2bl5d3ibp.fsf@gmail.com>
Hey, great! I was going to patch the example (was just reading the commit
guidelines) but I'll leave it in your hands then. Thanks!
Best,
On Tue, Aug 31, 2021 at 9:33 AM Daniel Fleischer <danflscr@gmail.com> wrote:
>
> Timothy [2021-08-31 Tue 19:27] wrote:
>
> > Hi Cassio,
> >
> >> Ah! Can’t believe I didn’t try that. Well, at least the docs can
> >> benefit from my confusion.
> >
> > Would you be interested in making a patch for the docs, or would you rather
> > leave that to someone else?
>
> Actually I want to do that. I had an idea to add a node (in org)
> "reminding" people that all mentions of regex refer to elisp regex,
> which could be different than what people usually know (PCRE) and point
> them toward the elisp regex node. I think this point can confuse non
> technical people when they are starting to use orgmode and there should
> be a mention in the org manual. Most notably are the alternation \|
> instead of | and \(...\) grouping instead of (...).
>
> Best,
>
>
> *Daniel Fleischer*
--
Cassio Koshikumo
next prev parent reply other threads:[~2021-08-31 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 20:12 [BUG] Creating sparse tree with regexp property matches Cassio Koshikumo
2021-08-25 21:03 ` Daniel Fleischer
2021-08-25 22:30 ` Cassio Koshikumo
2021-08-31 11:27 ` Timothy
2021-08-31 12:28 ` Daniel Fleischer
2021-08-31 12:41 ` Cassio Koshikumo [this message]
2021-08-31 12:56 ` Timothy
2021-08-31 20:31 ` Daniel Fleischer
2021-09-01 10:28 ` Timothy
2021-09-01 11:32 ` Daniel Fleischer
2021-09-02 6:35 ` [PATCH] " Daniel Fleischer
2021-09-16 15:01 ` Daniel Fleischer
2021-09-17 10:17 ` Timothy
2021-09-17 11:15 ` Daniel Fleischer
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=CAJP-4jMMtHb93mFyZo4GGsibZcOuE-dPKsvdg16wm-MKWp6UFQ@mail.gmail.com \
--to=ckoshikumo@gmail.com \
--cc=danflscr@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tecosaur@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).