> OrgStruct mode is no longer provided in Org.
I see, thanks!
PS Just found out about outshine and orgalist, gonna check them out.
пн, 1 июн. 2020 г. в 13:31, Nicolas Goaziou :
>
> Hello,
>
> Dmitrii Korobeinikov writes:
>
> >> M-x orgstruct-mode
> >
> >> I get the error:
> >
> >>
On Mon, Jun 1, 2020 at 4:16 AM Kyle Meyer wrote:
Daniel Kraus writes:
>
> > I use ob-sql with the :dbconnection param so I don't have my username
> and password in my org file.
> > But often I don't want to use the default database from the dbconnection
> alist but
> > rather specify it
Hello,
Dmitrii Korobeinikov writes:
>> M-x orgstruct-mode
>
>> I get the error:
>
>> command-execute: Autoloading file
>> /usr/share/emacs/site-lisp/org/org.elc failed to define function
>> orgstruct-mode
>
> Interesting, with --no-site-lisp flag there's no error and the
> orgstruct-mode seems
Matthew Lundin writes:
> stardiviner writes:
>
>> Matthew Lundin writes:
>>
>>>
>>> I think you also need to replace the newline with a space in the upper
>>> case version.
>>>
>> Supposed there is \n after #+end_src. I also checked the original version
>> before
>> that change commit. The
Bastien writes:
> Brandon Guttersohn writes:
>
>> So this patch is sort of a
>> new feature, but a trivial one.
>
> Agreed. Could you or Kevin propose a sentence to advertise this small
> enhancement in etc/ORG-NEWS?
Here goes nothing.
>From b18f6dc66ea4a05c95a4ee6825723da4beaa1c83 Mon Sep
Hi Bastien,
On 6/1/20, Bastien wrote:
> Hi Adam,
>
> Adam Porter writes:
>
>> The relatively recent moving of org-get-outline-path to org-refile.el
>> has caused breakage in Org itself in several places, e.g.
>>
>> https://lists.gnu.org/archive/html/emacs-orgmode/2020-04/msg00260.html
>>
Hi Mario,
Mario Frasca writes:
> myself, I recently posted a patch, received zero reaction, and have
> the impression it's now lost in the logs of this mailing list. indeed
> pretty inefficient!
Sorry for that.
As others have mentioned, Org developers are working on their free
time to
Kévin Le Gouguec writes:
> Absolutely. I've attached a patch to that effect.
I just realized that these let-bindings probably deserved explanatory
comments. Here is an updated patch:
>From f996ec3a10a845abae2fa463ab0ea7a761af1707 Mon Sep 17 00:00:00 2001
From:
Hi all,
I've developed an experimental tool to help everyone track confirmed
bugs, upcoming changes and releases and I've set it up for Org here:
https://updates.orgmode.org
It is based on this piece of software: https://github.com/bzg/woof
You can subscribe to all Org updates through this
Sorry, I've never submitted a patch before. Looking through this mailing
list, I see that you're supposed to attach the .patch file to the e-mail,
so here it is.
This patch adds a minor mode that makes emphasis markers be automatically
unhidden when the point is inside the region of emphasis and
Bastien writes:
> I've developed an experimental tool to help everyone track confirmed
> bugs, upcoming changes and releases
Here is what contributors/maintainers need to know:
To confirm a bug, reply to the bug report and add:
X-Woof-Bug: confirmed
To mark a bug as "fixed", reply in the
On 01/06/2020 10:53, Bastien wrote:
Let us know what would help you contribute more.
as mentioned, I would like to correct docstrings, refactor the code in a
few points, and add unit tests.
---
(defun org-plot/gnuplot-script (data-file num-cols params preface)
"Write a gnuplot script to
Kyle Meyer writes:
>> I think I've narrowed this down to org-open-file running "less
>> examples/att1/fileA" instead of visiting this file.
> [...]
>> Let-binding org-file-apps to '(("." . emacs)) makes the tests pass, but
>> I don't know if that's the way we want to solve this.
>
> Thanks for
Wow, that's fast!
Thanks
Le lun. 1 juin 2020 à 15:17, Nicolas Goaziou a
écrit :
> Hello,
>
> Vincent Picaud writes:
>
> > I just run into this small problem which is maybe a bug: I cannot PDF
> > export this small demo.org file.
>
> [...]
>
> > #+OPTIONS: ^:nil
> > #+TITLE: Maybe a bug
>
>
Hi all,
Bastien writes:
> C-TAB in Org is bound to `org-force-cycle-archived' to allow to cycle
> through archived subtrees.
>
> In the Emacs tab-bar mode, it is now bound to `tab-next', which needs
> to work globally.
>
> So Org's binding and tab-bar's one are in conflict, as reported here:
>
Hi Michael,
thanks for reporting this.
Michael Brand writes:
> Is this all intended behaviour?
Well, no, I think the current behavior is confusing.
> When I start with ~C-c C-c~ on [ of line A, Org seems to count list items:
> Then ~S-~ on line D seems to count subheadings:
> Then ~C-c C-c~
Hello Terje,
> I have now signed the FSF papers. Here is the updated patch on top of
> current master.
Great, thanks.
> Let me know if all looks good or if I need to make further changes or
> need to provide something else.
It looks good -- here is an updated patch with shorter lines.
The
Hi Eric,
Eric Abrahamsen writes:
> Maybe a first step would be changing `org-submit-bug-report' to submit
> the bug to debbugs, not to this mailing list?
I'd like to keep this mailing list as the central place to discuss
everything about Org, including bug reports.
When Org bugs are reported
Hi Anthony,
Anthony Carrico writes:
> Does org-mode have an issue tracker, to keep track of which issues
> are active, or is it just this mailing list?
thanks for asking.
I've skimmed through https://orgmode.org/worg/org-faq.html and the
question "Does org-mode have an issue tracker?" is
Hi Bastien,
in the meanwhile someone found the patch, and we are working on it.
thank you for the feedback!
but it stays confusing, and sure I get the point, people here are
volunteers, working on their free time, but precisely for this reason it
would be better if we could rely on some more
On Mon, Jun 01, 2020 at 11:28:48AM -0500, Mario Frasca wrote:
> On 01/06/2020 10:53, Bastien wrote:
> > Let us know what would help you contribute more.
>
> as mentioned, I would like to correct docstrings, refactor the code in a
> few points, and add unit tests.
>
> I've not been collecting them,
I also wholeheartedly agree with Matt and Detlef: I find emails to be
the best way to deal with bug reports.
Matthew Lundin writes:
> I agree wholeheartedly with everything Detlef says here. Due to life
> circumstances, I have only been able to participate intermittently on
> the mailing list
Vincent Picaud writes:
> Wow, that's fast!
PS: That's why Org does not need a traditional bug tracking tool ;)
--
Bastien
Hi Adam,
Adam Porter writes:
> The relatively recent moving of org-get-outline-path to org-refile.el
> has caused breakage in Org itself in several places, e.g.
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2020-04/msg00260.html
>
Hello Org's developpers,
Some time ago I tried to export in html form an org file containing many
src blocks and ended with the following message :
org-html-do-format-code: Buffer is read-only: #
After narrowing down my file here are the steps to reproduce :
emacs -q
(require 'htmlize) ;;
Hi Mario,
Mario Frasca writes:
> while working on my contribution, I'm also reading the code I'm adding
> to, and I am tempted to perform unrelated edits, like correcting a
> docstring to a function that does something, just not quite what the
> docstring says, or refactoring stuff in order to
Dear OrgMode Developers & Maintainers,
First of all, thank you s much for such a wonderful software! I am
using OrgMode every second and this is always a wonderful experience.
I just run into this small problem which is maybe a bug: I cannot PDF
export this small demo.org file.
Best,
On Monday, 1 Jun 2020 at 15:29, Bastien wrote:
> I believe we cannot fix this without a discussion on the design first.
Good to be able to discuss this. I won't repeat the options but will
give my own views as I do use statistic cookies quite a bit.
I would accept either 1 and/or 2 with or
Hello,
Vincent Picaud writes:
> I just run into this small problem which is maybe a bug: I cannot PDF
> export this small demo.org file.
[...]
> #+OPTIONS: ^:nil
> #+TITLE: Maybe a bug
[...]
>
> 2. [[(parameter_size)][parameter_size()]] blabla...
>
> #+begin_src cpp
> std::size_t
stardiviner writes:
> You're right, I updated the patch now. I really missed seeing
> that. :)
Applied, thanks!
--
Bastien
* lisp/org.el:
(org-auto-emphasis-unhide-at-point): Parameter that controls the
behavior of Org Auto Emphasis mode. It can be one of the values nil, t, and
'right-edge, and works similarly to the parameter
`prettify-symbols-unprettify-at-point' for `prettify-symbols-mode'.
Hi all,
Bastien writes:
> C-TAB in Org is bound to `org-force-cycle-archived' to allow to cycle
> through archived subtrees.
>
> In the Emacs tab-bar mode, it is now bound to `tab-next', which needs
> to work globally.
>
> So Org's binding and tab-bar's one are in conflict, as reported here:
>
Hi Stefan,
Stefan Kangas writes:
> Please find attached a patch to add a new function org-agenda-filter-set
> which allows you to specify the same strings as in the org-agenda-filter
> prompt directly from Lisp. It allows you to do things like:
I've seen problems with this new function when
Brandon Guttersohn writes:
> So this patch is sort of a
> new feature, but a trivial one.
Agreed. Could you or Kevin propose a sentence to advertise this small
enhancement in etc/ORG-NEWS?
--
Bastien
Kévin Le Gouguec writes:
> Thanks for the pointer, and for applying the patches!
>
FAILED ob-tangle/jump-to-org
FAILED test-org-attach/dir
I have had both tests failing for a while without understanding why,
if this gets fixed as a side-effect of the incomplete fix I made for
Hi Roland,
Roland Everaert writes:
> [QUESTION] -> [ANSWER]
> [BUG] -> ( [CONFIRMED] | [WONTFIX] | [SOLVED] )
> [CONFIRMED] -> ( [SOLVED] | [PLANNED] )
> [FEATURE] -> ( [WONTDO] | [PLANNED] | [IMPLEMENTED] )
> [PLANNED] -> ( [IMPLEMENTED] | [SOLVED] )
as others in this thread, I'm skeptical
Note that IIUC, for non-system includes to work, either
- the filenames must be absolute, or
- the compiler must be given -I arguments through org-babel-C-compiler.
This variable can be set (e.g. to "gcc -I .") with file or
directory-local variables. Should we promote this method in NEWS?
Hi Adam,
Adam Porter writes:
> I mostly agree with you. My request is simply that, when a change
> has the potential to break third-party packages, and it's a change,
> such as this one, that mostly moves code around for organizational
> purposes, that it be delayed until the next major
38 matches
Mail list logo
