+1 - I also think that this is the correct behavior, and that the
average user's expectations can be best fulfilled by making ":results output"
the default. Adding the option will make it more difficult to share code
blocks and documents.
Best regards,
Derek
On Thu, Feb 20 2020, Tim Cross
In an imenu drop-down list of a buffers contents, how can I get it to
show just the TODO status, and just show the sections title once the
TODO is removed, please?
Thanks
Sharon.
--
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts =
Bastien writes:
> Then, after you commit an edited version of these instructions, maybe
> Robert and Marcin can help reviewing and enhancing it to ensure it is
> self-sufficient and explicit enough?
I have pushed a (ever so) slightly edited version as new file in a
branch to worg here:
+1 - this is basically my feeling as well. I've spent the last couple of
days thinking about the additional option suggestion, but something just
didn't feel right to me. I think Nick has hit the nail on the head.
Adding the additional option seems to be making things more confusing.
The basic
Hi Bastien,
Bastien writes:
> Hi Diego,
>
> Diego Zamboni writes:
>
>> I'm late to the discussion so I apologize in advance, but this fix
>> seems counterintuitive to me. In my mind, for any shell code:
>>
>> - Return value: exit code of the last command
>> - Output: whatever the commands
Bastien writes:
> Hi Eric,
>
> Eric Abrahamsen writes:
>
>> I'll also note that, while this works perfectly well, every time I
>> refresh my custom agenda I see:
>>
>> Making org-agenda-tag-filter buffer-local while locally let-bound!
>
> Can you send enough information so that we can reproduce
Hi Jack,
Jack Kamm writes:
> I think this is more or less the case today, and we're on the same page
> here. Just wanted to make this goal explicit.
OK, thanks for the precision!
--
Bastien
Hi Eric,
Eric Abrahamsen writes:
> I'll also note that, while this works perfectly well, every time I
> refresh my custom agenda I see:
>
> Making org-agenda-tag-filter buffer-local while locally let-bound!
Can you send enough information so that we can reproduce the problem?
Thanks!
--
Eric Abrahamsen writes:
> Bastien writes:
>
>> Hi Eric,
>>
>> Eric Abrahamsen writes:
>>
>>> In my current Org, version 9.3.6-elpaplus, I need a "+" in front of a
>>> select tag, ie the "MAYBE" above needs to be "+MAYBE", otherwise nothing
>>> is selected at all.
>>
>> FWIW yes, this should be
Hi,
Bastien writes:
> Also, for included ob-*, the idea would be to use the mode that are
> bundled with Emacs core. For Python, it would mean that ob-python.el
> should support python.el, not python-mode.el.
I agree that ob-python.el should only rely on functionality from
python.el, and
Hi Karl,
Karl Voit writes:
> Can somebody estimate on the effort and potential negative
> implications (performance, caching issues, ...) when this feature
> would be extended, so that radio targets of foo.org also work[2] in
> foo.org_archive and vice versa?
Radio targets only work within the
Hi Karl,
Karl Voit writes:
> With disabled org-depend, it is working and finishes in ~5 minutes. With
> enabled org-depend it (sometimes) end up in an error as described.
Do you need org-depend when exporting?
If not, I simply suggest to turn org-depend off... or to let-bind
Hi Stardiviner,
stardiviner writes:
> I first created a very simple ob-php.el because it does not exist in Org Mode.
> But it's really just a very simple code. Now a friend of mine is using it, I
> wish to improve it. Seems current ob-php.el does not support some cases like
> PHP
> code
Bastien writes:
> Hi Eric,
>
> Eric Abrahamsen writes:
>
>> In my current Org, version 9.3.6-elpaplus, I need a "+" in front of a
>> select tag, ie the "MAYBE" above needs to be "+MAYBE", otherwise nothing
>> is selected at all.
>
> FWIW yes, this should be "+MAYBE".
Thanks for confirming!
Hi all,
in future releases of Org, we will move toward stricter rules on what
to accept as ob-* libraries and what modes these libraries should rely
upon.
This was briefly mentioned in this email:
https://lists.gnu.org/archive/html/emacs-orgmode/2020-02/msg00714.html
For example, we can have a
Hi!
Only recently, I found radio targets[1] very handy to implement a
glossary within an Org file. This way, any instance of "PIM" can be
linked to one single definition of "- <<>> :: Personal
Information Management" for example.
My question (and feature request):
Can somebody estimate on the
Hi Eric,
Eric Abrahamsen writes:
> In my current Org, version 9.3.6-elpaplus, I need a "+" in front of a
> select tag, ie the "MAYBE" above needs to be "+MAYBE", otherwise nothing
> is selected at all.
FWIW yes, this should be "+MAYBE".
--
Bastien
Hi stardiviner,
stardiviner writes:
> I found ob-python does not support ":results pp" pretty print result. And
> Python
> has a module "pprint". What about add support this?
Well, there is code in ob-python.el that uses the pprint module when
":results pp", but I must admit I've never used
Stig Brautaset writes:
> Hi Bastien,
>
> Bastien writes:
>>> I can easily do this in the list of TODOs, with a tag search. However, I
>>> haven't figured out how to do this for the agenda. Is it possible? If
>>> so, how?
>>
>> From what I understand, check `org-agenda-tag-filter' to see how to
,
On 20.02.20 06:45, stardiviner wrote:
Hi,
python-mode.el developer here.
Since python.el is built-in to Emacs, I think that things should
continue to work for python-mode.el users, even if we entirely switch
over to only using python.el.
Thanks supporting python-mode.el. Both python-modes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I have a requirement, I want to display file: link's file type info on the link.
For example, an Org file: link
#+begin_src org
[[file:~/Org/logo.png][logo]]
[[file:~/Org/document.pdf][document]]
[[file:~/Org/book.epub][book]]
#+end_src
I want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I found ob-python does not support ":results pp" pretty print result. And Python
has a module "pprint". What about add support this?
- --
[ stardiviner ]
I try to make every word tell the meaning what I want to express.
Blog:
stardiviner writes:
>> Can you suggest the author to add this to
>> https://orgmode.org/worg/org-hacks.html ?
>
> Pushed to Worg now. Done. :)
Thanks!
--
Bastien
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bastien writes:
> stardiviner writes:
>
>> (add-hook 'org-agenda-finalize-hook #'org-agenda-time-grid-colorful-spacing)
>
> FWIW I don't think this should go in Org's core, it is a useful
> command to customize Org agenda colors.
>
> Can you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bastien writes:
> Hi Stardiviner,
>
> stardiviner writes:
>
>> I reconsidered this patch, what about make it an minor-mode for Org
>> Mode and put it in contrib/ directory? WDYT?
>
> I suggest using worg/org-hacks.org instead: this describes
I first created a very simple ob-php.el because it does not exist in Org Mode.
But it's really just a very simple code. Now a friend of mine is using it, I
wish to improve it. Seems current ob-php.el does not support some cases like PHP
code "include ".
Current patch is a more flexible solution.
* Bastien wrote:
> Hi Karl,
Hi,
> another suggestion: just send us a minimal extract of your files so
> that we see how org-depend is called, together with what you do and
> what goes wrong when you do it. Perhaps this will lead to something.
Sure.
>
> > However, hiding emphasis and macro markers can make editing text at
> > the boundaries of emphasized text non-intuitive, which I can imagine
> > might frustrate some new users, so that should probably be carefully
> > considered.
>
+1e6
> Interestingly, hiding emphasis and macro markers
Hi Karl,
another suggestion: just send us a minimal extract of your files so
that we see how org-depend is called, together with what you do and
what goes wrong when you do it. Perhaps this will lead to something.
I've never used org-edna, I'm curious to know if there are many users.
Thanks,
Hi Nicolas,
Nicolas Goaziou writes:
> This second patch removes most of the "attachment" leakage in the code
> base (mainly "org-element.el" and "ox-*.el"). The features should be the
> same as before. Let me know if there's anything wrong.
Thanks a lot -- feel free to apply it when you think
Hi,
* Bastien wrote:
>
> Karl Voit writes:
>
>> A couple days ago, the issue re-appeared (with org-depend being
>> active again). To me, this is a clear indicator, that the issue is
>> content-related and not config/binary-related:
>
> Can you bisect and deduce what part of your contents is
Following up,
Nicolas Goaziou writes:
> This is the first part of the suggested changes. These do not touch
> attachment modifications, but rather improve the tooling in "ol.el".
This second patch removes most of the "attachment" leakage in the code
base (mainly "org-element.el" and
On 2020-02-19 18:49, Nicolas Goaziou writes:
> Alan Schmitt writes:
>
>> I understand, and I can be careful (and easily fix the link if needed).
>> If `org-store-link' could do it for me, that would be perfect.
>
> I pushed some changes to `org-store-link' in order to fix this. Please
> report
33 matches
Mail list logo
