From: Samuel Wales <samologist@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: text search and restriction lock bugs
Date: Thu, 7 Sep 2017 15:44:30 -0700 [thread overview]
Message-ID: <CAJcAo8tre=mKDnwXhcF7xNnS1jfaxdROmgoM2A6XGT5R0BE8fg@mail.gmail.com> (raw)
In-Reply-To: <877exazk3d.fsf@nicolasgoaziou.fr>
On 9/7/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> from org-agenda-text-search-extra-files? imo it should not.
>
> Agreed. Fixed.
thank you.
>> 2.
>>
>> if you remove the restriction lock and refresh the agenda,
>> it will produce different results.
>>
>> imo, should act as if the restriction lock were still in place. g
>> should refresh with the settings that were present at invocation.
>> sometimes you change buffer name, and run a new agenda, so that you
>> can have 2 agendas, one restricted and one not.
>
> Not sure I agree.
not able to convey my intuitions adequately atm.
>
>> the restriction lock is not fontified nicely so it can be desirable to
>> remove it for editing.
>
> Is this a different bug report?
no, haven't thought about it.
>> remove-duplicates. imo the agenda could do
> Agreed. Fixed.
thank you.
--
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>
The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.
"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.
next prev parent reply other threads:[~2017-09-07 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 21:42 text search and restriction lock bugs Samuel Wales
2017-09-07 13:58 ` Nicolas Goaziou
2017-09-07 22:44 ` Samuel Wales [this message]
2021-02-28 22:06 ` Samuel Wales
2021-03-27 23:02 ` Samuel Wales
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='CAJcAo8tre=mKDnwXhcF7xNnS1jfaxdROmgoM2A6XGT5R0BE8fg@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.