Oh wow Karl, lot's of 'hidden' gems there. Not related to this thread but I
specially liked `lazyblorg`, I actually had a very similar idea and was
about to develop something like that, you saved me a bunch of time :)
On Mon, Oct 1, 2018 at 3:57 PM Samuel Wales wrote:
> market more :]
>
> or you
Am 03.10.18 um 13:45 schrieb Marco Wahl:
> My git fu was not strong enough and so the "next" branch is a bit messy
> right now. (I tried to activate a local clean version of the "next"
> branch.)
>
> I thought I could easily rollback the mess I created by going back to
> the git node 3c8fd4fa7 wh
>> My git fu was not strong enough and so the "next" branch is a bit messy
>> right now. (I tried to activate a local clean version of the "next"
>> branch.)
>> [...]
>> Can someone help to clean up the "next" branch, please?
>
> I think I cleaned it.
Thank you so much!
> To prevent further co
Hello,
Christoph Michelbach writes:
> I noticed that a table as attached to this email (also available here:
> https://p
> astebin.com/AG7pwcq1) breaks org-mode's automatic adjustment of tables when
> pressing tab.
>
> To reproduce the problem, simply follow these steps:
> 1. Load the file and
Hello,
Marco Wahl writes:
> Hello fellow Orgers,
>
> This is more an internal issue about the repo and in particular the
> "next" branch.
>
> My git fu was not strong enough and so the "next" branch is a bit messy
> right now. (I tried to activate a local clean version of the "next"
> branch.)
Hello,
Matthias Paulmier writes:
> I think I get the logic behind it. The problem is the inconsistency it
> creates for the viewer. Does it really matter for them if I wrote my
> footnote inline or not?
Inline footnotes are now wrapped within a paragraph. Thank you.
Regards,
--
Nicolas Goazi
On 2018-10-03, at 12:51, Nicolas Goaziou wrote:
> Hello,
>
> Marcin Borkowski writes:
>
>> I attach a patch with a more verbose docstring.
>>
>> It is perhaps still not ideal - in particular, the warning is not
>> visible in the Customize interface - but I do not think this is a big
>> deal.
Hello fellow Orgers,
This is more an internal issue about the repo and in particular the
"next" branch.
My git fu was not strong enough and so the "next" branch is a bit messy
right now. (I tried to activate a local clean version of the "next"
branch.)
I thought I could easily rollback the mess
Hello,
Marcin Borkowski writes:
> I attach a patch with a more verbose docstring.
>
> It is perhaps still not ideal - in particular, the warning is not
> visible in the Customize interface - but I do not think this is a big
> deal. My line of thinking is that:
>
> - if a user wants to change th
Hello,
> That aside, the wording of the second sentence could be clearer.
> My humble suggestion:
>
> "If non-nil, always offer completion for all tags of all agenda files.
> Setting this variable locally allows for dynamic generation of tag
> completions in capture buffers."
Applied. Thank you.
Eivind Otto Hjelle writes:
> I thought I had updated emacs to the latest version, but apparently not.
> After upgrading to emacs-26 the command org-in-src-block-p works as
> expected. Thanks!
Thanks for checking. Closing.
Regards
Robert
>> I just pushed command `org-info-find-node' bound to "C-c C-x I" by
>> default for Org files and agenda buffers.
>
> Nitpick: Would you mind removing the dangling parens left in the
> function?
Okay, thanks. Consider it DONE.
> Also, I'd like to avoid making changes to "master" branch. It shou
12 matches
Mail list logo
