Re: Removed variables ‘org-agenda-skip-comment-trees’ and ‘org-agenda-skip-archived-trees’
As another data point, they seem to be there for me - at least when I do search for describe variable. Emacs Version: GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.23, cairo version 1.16.0) of 2020-11-19 Org Version: Org mode version 9.4 (9.4-41-g9bb930-elpaplus @ /home/tim/.emacs.d/elpa/28.0/develop/org-plus-contrib-20201116/) Tim wlharv...@mac.com writes: > Searching for the variables leads to a failed search, both from > 'describe-variable' and 'isearch-forward' in 'org.el'. I am using > > GNU Emacs 28.0.50 (build 1, x86_64-apple-darwin19.6.0, NS appkit-1894.60 > Version 10.15.6 (Build 19G2021)) > of 2020-09-14 > > > > > > > >> On Nov 19, 2020, at 8:28 PM, Kyle Meyer wrote: >> >> wlharv...@mac.com writes: >> >>> In Org 9.4, Manual section 11 Agenda Views, second to last paragraph, >>> neither of the referenced variables appears to exist. >> >> Hmm, what leads you to say that? >> >> $ git describe master >> release_9.4-134-g0d525cbc7 >> >> $ git grep 'org-agenda-skip-\(comment\|archived\)-trees' master >> master:doc/org-manual.org: #+vindex: org-agenda-skip-archived-trees >> master:doc/org-manual.org: ~org-agenda-skip-archived-trees~, in which case >> these trees are >> master:doc/org-manual.org:#+vindex: org-agenda-skip-comment-trees >> master:doc/org-manual.org:#+vindex: org-agenda-skip-archived-trees >> master:doc/org-manual.org:setting ~org-agenda-skip-comment-trees~ and >> master:doc/org-manual.org:~org-agenda-skip-archived-trees~ to ~nil~. >> master:lisp/org-agenda.el:(defcustom org-agenda-skip-comment-trees t >> master:lisp/org-agenda.el: (and org-agenda-skip-archived-trees (not >> org-agenda-archives-mode) >> master:lisp/org-agenda.el: (and org-agenda-skip-comment-trees >> master:lisp/org.el:(defcustom org-agenda-skip-archived-trees t >> master:lisp/org.el:(defvar org-agenda-skip-comment-trees) >> master:lisp/org.el:(org-agenda-skip-archived-trees (memq 'archive >> skip)) >> master:lisp/org.el:(org-agenda-skip-comment-trees (memq 'comment >> skip)) >> master:lisp/org.el: (when org-agenda-skip-archived-trees -- Tim Cross
Re: Removed variables ‘org-agenda-skip-comment-trees’ and ‘org-agenda-skip-archived-trees’
Hmm, I restarted Emacs, and the variables show up. My apologies. I upgraded a day or two ago, but didn’t restart until now. Wesley > On Nov 19, 2020, at 8:28 PM, Kyle Meyer wrote: > > wlharv...@mac.com writes: > >> In Org 9.4, Manual section 11 Agenda Views, second to last paragraph, >> neither of the referenced variables appears to exist. > > Hmm, what leads you to say that? > > $ git describe master > release_9.4-134-g0d525cbc7 > > $ git grep 'org-agenda-skip-\(comment\|archived\)-trees' master > master:doc/org-manual.org: #+vindex: org-agenda-skip-archived-trees > master:doc/org-manual.org: ~org-agenda-skip-archived-trees~, in which case > these trees are > master:doc/org-manual.org:#+vindex: org-agenda-skip-comment-trees > master:doc/org-manual.org:#+vindex: org-agenda-skip-archived-trees > master:doc/org-manual.org:setting ~org-agenda-skip-comment-trees~ and > master:doc/org-manual.org:~org-agenda-skip-archived-trees~ to ~nil~. > master:lisp/org-agenda.el:(defcustom org-agenda-skip-comment-trees t > master:lisp/org-agenda.el: (and org-agenda-skip-archived-trees (not > org-agenda-archives-mode) > master:lisp/org-agenda.el: (and org-agenda-skip-comment-trees > master:lisp/org.el:(defcustom org-agenda-skip-archived-trees t > master:lisp/org.el:(defvar org-agenda-skip-comment-trees) > master:lisp/org.el:(org-agenda-skip-archived-trees (memq 'archive > skip)) > master:lisp/org.el:(org-agenda-skip-comment-trees (memq 'comment > skip)) > master:lisp/org.el: (when org-agenda-skip-archived-trees
Re: Removed variables ‘org-agenda-skip-comment-trees’ and ‘org-agenda-skip-archived-trees’
'(org-version)' produces: 9.4-41-g9bb930-elpaplus from org-plus-contrib-20201116 > On Nov 19, 2020, at 8:28 PM, Kyle Meyer wrote: > > wlharv...@mac.com writes: > >> In Org 9.4, Manual section 11 Agenda Views, second to last paragraph, >> neither of the referenced variables appears to exist. > > Hmm, what leads you to say that? > > $ git describe master > release_9.4-134-g0d525cbc7 > > $ git grep 'org-agenda-skip-\(comment\|archived\)-trees' master > master:doc/org-manual.org: #+vindex: org-agenda-skip-archived-trees > master:doc/org-manual.org: ~org-agenda-skip-archived-trees~, in which case > these trees are > master:doc/org-manual.org:#+vindex: org-agenda-skip-comment-trees > master:doc/org-manual.org:#+vindex: org-agenda-skip-archived-trees > master:doc/org-manual.org:setting ~org-agenda-skip-comment-trees~ and > master:doc/org-manual.org:~org-agenda-skip-archived-trees~ to ~nil~. > master:lisp/org-agenda.el:(defcustom org-agenda-skip-comment-trees t > master:lisp/org-agenda.el: (and org-agenda-skip-archived-trees (not > org-agenda-archives-mode) > master:lisp/org-agenda.el: (and org-agenda-skip-comment-trees > master:lisp/org.el:(defcustom org-agenda-skip-archived-trees t > master:lisp/org.el:(defvar org-agenda-skip-comment-trees) > master:lisp/org.el:(org-agenda-skip-archived-trees (memq 'archive > skip)) > master:lisp/org.el:(org-agenda-skip-comment-trees (memq 'comment > skip)) > master:lisp/org.el: (when org-agenda-skip-archived-trees
Re: Bug: org-clone-subtree-with-time-shift throws error [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]
skap...@pm.me writes: > Summary: using org-clone-subtree-with-time-shift on an entry with the > ID property and a timestamp causes an error or does not create > different IDs, which worked before 27.1. > > Long Description: > > I have a calendar file with a lot of entries, but I slimmed it down to a MWE: > > === begin MWE === [...] Thanks for detailed report and nice reproduction steps. I believe this has already been addressed by c716b7c08 (org-id: Allow file name to be overridden on ID creation, 2020-04-16), which was included in the 9.3.7 release. related thread: https://orgmode.org/list/87a73caayj.fsf@phaktory/T/#u
Re: Removed variables ‘org-agenda-skip-comment-trees’ and ‘org-agenda-skip-archived-trees’
wlharv...@mac.com writes: > In Org 9.4, Manual section 11 Agenda Views, second to last paragraph, > neither of the referenced variables appears to exist. Hmm, what leads you to say that? $ git describe master release_9.4-134-g0d525cbc7 $ git grep 'org-agenda-skip-\(comment\|archived\)-trees' master master:doc/org-manual.org: #+vindex: org-agenda-skip-archived-trees master:doc/org-manual.org: ~org-agenda-skip-archived-trees~, in which case these trees are master:doc/org-manual.org:#+vindex: org-agenda-skip-comment-trees master:doc/org-manual.org:#+vindex: org-agenda-skip-archived-trees master:doc/org-manual.org:setting ~org-agenda-skip-comment-trees~ and master:doc/org-manual.org:~org-agenda-skip-archived-trees~ to ~nil~. master:lisp/org-agenda.el:(defcustom org-agenda-skip-comment-trees t master:lisp/org-agenda.el: (and org-agenda-skip-archived-trees (not org-agenda-archives-mode) master:lisp/org-agenda.el: (and org-agenda-skip-comment-trees master:lisp/org.el:(defcustom org-agenda-skip-archived-trees t master:lisp/org.el:(defvar org-agenda-skip-comment-trees) master:lisp/org.el:(org-agenda-skip-archived-trees (memq 'archive skip)) master:lisp/org.el:(org-agenda-skip-comment-trees (memq 'comment skip)) master:lisp/org.el: (when org-agenda-skip-archived-trees
Re: [PATCH] repeat cookies should be in the same order as the repeats
Kyle Meyer writes: > Thanks for the patch. > >> [PATCH] repeat cookies should be in the same order as the repeats I've amended the commit (as requested off-list) and pushed (5272d97e5). Thanks again Dieter.
Re: [PATCH] doc/org-manual.org: add reference to org-table-transpose-table-at-point
Greg Minshall writes:
> Kyle, thanks. yes, blind copy and paste. i'm not a git-format-patch
> expert, so let me know if this is the wrong format (i see some people
> include inline, whereas others attach a file -- is one easier to handle
> than the other?)
Either way is fine on this list, and, while I can of course only speak
for myself, I don't find one harder to handle than the other,
particularly for one-patch series. It comes down to whichever is
easiest for the sender.
With a single inline patch like yours, the placement of the text that
isn't meant for the commit message needs some special consideration. If
your message is fed to 'git am', the quoted text above would go into the
commit message, so the person applying would need to amend it to clean
it up.
There are two options to deal with this extra text: 1) place it under
the "---" at the end of the commit message or 2) add a "-- >8 --"
between the extra text and the main commit message text, which can be
automatically stripped out by passing -c to 'git am'. The first option
works well for things like extra notes but reads a bit awkward for text
that would more naturally lead the message.
Below is an example of the second method. The From header is only
needed to override my From header from the actual mail. I've added a
changelog entry.
Pushed as a5d765481. Thanks!
-- >8 --
From: Greg Minshall
* doc/org-manual.org (Built-in Table Editor): Add
org-table-transpose-table-at-point to list of miscellaneous commands.
---
doc/org-manual.org | 5 +
1 file changed, 5 insertions(+)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 0a3a8c6cd..34b0164fc 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -1649,6 +1649,11 @@ *** Miscellaneous
the buffer. You can activate this minor mode by default by setting
the option ~org-table-header-line-p~ to ~t~.
+- {{{kbd(M-x org-table-transpose-table-at-point)}}} ::
+
+ #+findex: org-table-transpose-table-at-point
+ Transpose the table at point and eliminate hlines.
+
** Column Width and Alignment
:PROPERTIES:
:DESCRIPTION: Overrule the automatic settings.
base-commit: 104d92199e3cba7cefd504f24c3610031fa384de
--
2.29.2
Removed variables ‘org-agenda-skip-comment-trees’ and ‘org-agenda-skip-archived-trees’
In Org 9.4, Manual section 11 Agenda Views, second to last paragraph, neither of the referenced variables appears to exist. The manual should be updated; is there a different mechanism for these actions now? Regards, Wesley
Re: Clock tables and two ways to categorize tasks
Hello, Thank you for the patch from reddit and gist on categorizing tasks in the clocktable. Is there a way, the :formula % will also work on the *Category Time*, that will be really handy in trying to find out category based time clocking? Thanks and have a nice day! Bala https://balaramadurai.net
updates website broken
https://updates.orgmode.org/ is broken, unfortunately. Not sure how to address that, but guessing that this email list will know. -justin
Re: [PATCH] org-table: Add mode flag to enable Calc units simplification mode
On 19/11/2020 06:58, Kyle Meyer wrote: > Daniele Nicolodi writes: > >> Hello, >> >> I don't think this is what is holding up review of these patches, but, I >> recently completed the paperwork for copyright assignment to the FSF. > > Thanks for this series (and thanks to Eric for the feedback in the > previous thread). I'm sorry for the slow response. > > Quickly scanning through and playing around with it, it looks nicely > done. I'll put aside some time this weekend to give it a closer review. Thanks for having a look, Kyle. Cheers, Dan
Re: [HELP} Capture Template
Tim Cross writes:
> I'm trying to get a capture template to work, but without luck. Not sure
> what I'm doing wrong, but figured someone on this list could help by
> pointing out my probably obvious error.
>
> The template is
>
> ("e" "expense" entry
> (file+headline "~/Documents/org-data/refile.org" "Expenses")
> "* Expense: %^{Description} :EXPENSE:\n\n | Date | %u |\n | Description |
> %\1 |\n | Amount | %^{Amount} |\n"
> :empty-line-after 1)
>
> The problem is with the %\1 expansion. According to the docs, the %\N
> expansion is replaced with the Nth %^{PROMPT} input. i.e. %\1 should be
> the data from the 1st %^{PROMPT} expansion (in this case
> %^{Description}.
>
> The problem is, it isn't. Instead, I get %^A as the result instead of
> the text I enter with the first %^{Description} expansion. The rest of
> the template works fine.
>
> Anyone got any ideas?
What about a further backslash? I.e. use %\\1 instead of %\1?
Ciao, Marco
[HELP} Capture Template
I'm trying to get a capture template to work, but without luck. Not sure
what I'm doing wrong, but figured someone on this list could help by
pointing out my probably obvious error.
The template is
("e" "expense" entry
(file+headline "~/Documents/org-data/refile.org" "Expenses")
"* Expense: %^{Description} :EXPENSE:\n\n | Date | %u |\n | Description | %\1
|\n | Amount | %^{Amount} |\n"
:empty-line-after 1)
The problem is with the %\1 expansion. According to the docs, the %\N
expansion is replaced with the Nth %^{PROMPT} input. i.e. %\1 should be
the data from the 1st %^{PROMPT} expansion (in this case
%^{Description}.
The problem is, it isn't. Instead, I get %^A as the result instead of
the text I enter with the first %^{Description} expansion. The rest of
the template works fine.
Anyone got any ideas?
Tim
--
Tim Cross
Re: [PATCH] Remove redundant 'function's around lambda
On Thu, 19 Nov 2020 at 14:51, Stefan Kangas wrote: > Neil Jerram writes: > > >> I've been working on removing redundant `function' around `lambda' in > >> Emacs core, > > > > I'm slightly curious about the history and reasoning around this. If I > > understand correctly, (lambda ...) on its own has always worked, and it's > > never been strictly necessary to add (quote ...) or (function ...) around > > it. Then sometime (Emacs 19 or later, I think) it started being > > recommended to use (function ...). > > > > Do you know why that recommendation started, and should I understand that > > the reasoning for it has now evaporated? > > Correct, there is no reason to do this. > > I don't know the history here, and there are people on emacs-devel that > would know better. > > I _suspect_ that the byte-compiler first got the capability to optimize > calls to anonymous functions, but that it required to explicitly marked > as such with `function'. Later, it grew the capability to recognize > lambda as such automatically. But I don't know if that is correct; it's > just a guess. In any case, they are no longer needed as lambda and > lambda+function are equivalent. > > (Note that the worst thing here is to do `(quote (lambda ...))' as that > defeats byte-compiler optimizations altogether.) > Many thanks Stefan!
Re: Clock tables and two ways to categorize tasks
Marcin Borkowski writes: > Hi all, > > here's the problem I'd like to solve. I clock various tasks, and then > generate a clock table. So far, so good. But now I'd like to know > better where my time goes. Most tasks I do have a few similar > components: discussion/research, writing code, testing, etc. I thought > that I could create subheadlines under each of the tasks and give them > tags like :discuss:, :code:, :test:, :debug: and so on. (Not very > convenient, but doable, maybe with a bit of Elisp to automate the > process.) > > Now, I'd like to prepare two clock tables: one where I see how much time > every task took, and one where I can see how much time I spent coding, > testing, debugging, emailing etc. I can see in the docs that there is > the ~:match~ option, but if I understand it correctly, it can only > restrict the table to /one/ tag, so I'd need to have as many tables as > I have tags - not optimal. > > Any ideas? Should I use something else than tags for that? > Although I haven't tried it, I think you can have multiple tags. You should be able to do something like +TEST+DEBUG-DISCUSS which would give you those tasks with tags :TEST: and :DEBUG: but not :DISCUSS: Have a look at the 'Matching tags and properties" section in the manual (under the agenda section). Another approach (actually the one I use) is to put things at different levels. So at level 1 is the Tasks heading, at level 2 is each TODO at level 3 is each subtask and at level 4 are the task activities ( Research, Code, Meetings, Testing, Documentation). My main clock table has :maxlevel 4, which shows a complete breakdown while the table I use for invoicing (where I only want to show total time, main task time and sub-task times, but not the level 4 stuff) has :maxlevel 3. Actually, I lie a bit. My current invoicing approach actually uses a custom :formatter function so that my invoice clock table has columns for rate, amount and total amount. However, the :maxlevel approach was where I started! -- Tim Cross
Re: Clock tables and two ways to categorize tasks
Hi Marcin, I tried to solve this issue for myself. My first attempt to solve it was to understand which tags are interesting and then make a template with as many tables as there were interesting tag combinations. But then I faced another problem: sometimes I am using different set of tags and templates don't work as good as they could. To mitigate that problem, I've tried different approach. I made a small package that generates me reports for past week or past month. It's working for me, but there are a lot of rough edges around it. Basically it collects headers with clocks, copies them to separate file, rearrange them and generate clock tables. You can try it here: https://github.com/mskorzhinskiy/org-ir Another way would be to write your own clock table sorter. See this post on reddit: https://www.reddit.com/r/emacs/comments/jp5ear/sorting_org_clocktables_by_category_instead_of/ And just for future references, in case Reddit someday will go down: Code from /u/jp5ear: https://gist.github.com/blockynight/5eebe8323b68e02f436c0440320dc926 Org-mode manual: https://orgmode.org/manual/The-clock-table.html (see :formatter parameter) Mikhail Skorzhinskii Marcin Borkowski writes: Hi all, here's the problem I'd like to solve. I clock various tasks, and then generate a clock table. So far, so good. But now I'd like to know better where my time goes. Most tasks I do have a few similar components: discussion/research, writing code, testing, etc. I thought that I could create subheadlines under each of the tasks and give them tags like :discuss:, :code:, :test:, :debug: and so on. (Not very convenient, but doable, maybe with a bit of Elisp to automate the process.) Now, I'd like to prepare two clock tables: one where I see how much time every task took, and one where I can see how much time I spent coding, testing, debugging, emailing etc. I can see in the docs that there is the ~:match~ option, but if I understand it correctly, it can only restrict the table to /one/ tag, so I'd need to have as many tables as I have tags - not optimal. Any ideas? Should I use something else than tags for that? TIA, -- --- Mikhail Skorzhinskii
Re: [PATCH] Remove redundant 'function's around lambda
Neil Jerram writes: >> I've been working on removing redundant `function' around `lambda' in >> Emacs core, > > I'm slightly curious about the history and reasoning around this. If I > understand correctly, (lambda ...) on its own has always worked, and it's > never been strictly necessary to add (quote ...) or (function ...) around > it. Then sometime (Emacs 19 or later, I think) it started being > recommended to use (function ...). > > Do you know why that recommendation started, and should I understand that > the reasoning for it has now evaporated? Correct, there is no reason to do this. I don't know the history here, and there are people on emacs-devel that would know better. I _suspect_ that the byte-compiler first got the capability to optimize calls to anonymous functions, but that it required to explicitly marked as such with `function'. Later, it grew the capability to recognize lambda as such automatically. But I don't know if that is correct; it's just a guess. In any case, they are no longer needed as lambda and lambda+function are equivalent. (Note that the worst thing here is to do `(quote (lambda ...))' as that defeats byte-compiler optimizations altogether.)
Windows org-capture path to file
Hello,
i try to use org-capture but my files under D:\\ are not recognized. The
problem is only for org-capture for agenda-list and initial buffer
choice it works.
my configuration:
'(initial-buffer-choice "d:/Led/02_Organisation/Orgzlyphone/aufgaben.org")
'(org-agenda-files '("d:/Led/02_Organisation/Orgzlyphone/aufgaben.org"))
'(org-capture-templates
'(("t" "TODO-Entry" entry (file+headline
"d:/Led/02_Organisation/Orgzlyphone/aufgaben.org" "*aktuelle Aufgaben*")
"** TODO %?\\n %i\\n %a"
I try to workaround with a symlink but that didnt work either so there
it said that the buffer has no writing access.
'(("t" "TODO-Entry" entry (file+headline
"~/.emacs.d/Orgzlyphone.lnk/aufgaben.org" "*aktuelle Aufgaben*")
"** TODO %?\\n %i\\n %a"
Any Ideas?
Greatings
Thorgrimsson
--
Sebastian Pisot
Lange Point 5
85354 Freising
0160 2768749
s.l.pi...@posteo.de
Clock tables and two ways to categorize tasks
Hi all, here's the problem I'd like to solve. I clock various tasks, and then generate a clock table. So far, so good. But now I'd like to know better where my time goes. Most tasks I do have a few similar components: discussion/research, writing code, testing, etc. I thought that I could create subheadlines under each of the tasks and give them tags like :discuss:, :code:, :test:, :debug: and so on. (Not very convenient, but doable, maybe with a bit of Elisp to automate the process.) Now, I'd like to prepare two clock tables: one where I see how much time every task took, and one where I can see how much time I spent coding, testing, debugging, emailing etc. I can see in the docs that there is the ~:match~ option, but if I understand it correctly, it can only restrict the table to /one/ tag, so I'd need to have as many tables as I have tags - not optimal. Any ideas? Should I use something else than tags for that? TIA, -- Marcin Borkowski http://mbork.pl
Re: [bug] Export to latex truncates long subsections (WE attached)
On Thursday, 19 Nov 2020 at 22:28, Tim Cross wrote: > I realised after posting that when this first came up some time back, > the other suggestion I made, which might still be valid, would be to add > another document 'class' to org-latex-classes which includes the snippet > by default. Then those who want or need this change could just add a > #+LATEX_CLASS line to their org file. That would be a good solution, say having a todo document class. -- : Eric S Fraga via Emacs 28.0.50, Org release_9.4-118-g2a4578.dirty
Re: [bug] Export to latex truncates long subsections (WE attached)
Eric S Fraga writes: > On Thursday, 19 Nov 2020 at 11:41, Vladimir Nikishkin wrote: >> Would the latex snippet in this thread be a good candidate for >> inclusion into org as a canned trick? > > No, please do not have this as default behaviour. It would break normal > documents. In the most innocuous case, it would allow documents to have > headings as the last part of a page with the text on the next page, a > typesetting faux pas (looking rather ugly). LaTeX documents look > inherently nicer than the typical word processed document because LaTeX > actually adjusts spacing of not only within lines but also between lines > and paragraphs to have the page look good. > > As Tim has suggested, adding this snippet to Worg would be useful and > maybe an item in the FAQ. As well, it might be useful to suggest > checkbox lists for people that want to export a long TODO list (which > might not be appropriate for all, of course). > I realised after posting that when this first came up some time back, the other suggestion I made, which might still be valid, would be to add another document 'class' to org-latex-classes which includes the snippet by default. Then those who want or need this change could just add a #+LATEX_CLASS line to their org file. Tim -- Tim Cross
Re: [bug] Export to latex truncates long subsections (WE attached)
2020-11-19 Vladimir Nikishkin wrote:
#+begin_src latex
\usepackage{xpatch}
\makeatletter
% This is not recommended, because it can break several things
\xpatchcmd{\@afterheading}{\@nobreaktrue}{\@nobreakfalse}{%
\typeout{WARNING: \string\@afterheading\space broken}%
}{%
\@latexerr{ERROR: Cannot patch \string\@afterheading}\@ehd%
}
\makeatother
#+end_src
Maybe introducing negative penalty *before* subsections would allow page
breaks without undesired splitting between usual headers and immediately
following paragraphs. I have not checked it, it is just an idea. I agree
that such tricks should not be enabled by default.
Re: [PATCH] Remove redundant 'function's around lambda
On Tue, 17 Nov 2020 at 17:08, Stefan Kangas wrote: > I've been working on removing redundant `function' around `lambda' in > Emacs core, I'm slightly curious about the history and reasoning around this. If I understand correctly, (lambda ...) on its own has always worked, and it's never been strictly necessary to add (quote ...) or (function ...) around it. Then sometime (Emacs 19 or later, I think) it started being recommended to use (function ...). Do you know why that recommendation started, and should I understand that the reasoning for it has now evaporated? Best wishes, Neil
Re: [bug] Export to latex truncates long subsections (WE attached)
On Thursday, 19 Nov 2020 at 11:41, Vladimir Nikishkin wrote: > Would the latex snippet in this thread be a good candidate for > inclusion into org as a canned trick? No, please do not have this as default behaviour. It would break normal documents. In the most innocuous case, it would allow documents to have headings as the last part of a page with the text on the next page, a typesetting faux pas (looking rather ugly). LaTeX documents look inherently nicer than the typical word processed document because LaTeX actually adjusts spacing of not only within lines but also between lines and paragraphs to have the page look good. As Tim has suggested, adding this snippet to Worg would be useful and maybe an item in the FAQ. As well, it might be useful to suggest checkbox lists for people that want to export a long TODO list (which might not be appropriate for all, of course). thank you, eric -- : Eric S Fraga via Emacs 28.0.50, Org release_9.4-118-g2a4578.dirty
Re: [bug] Export to latex truncates long subsections (WE attached)
Am 19.11.20 um 05:58 schrieb Tim Cross:
Vladimir Nikishkin writes:
So what is the status of this story?
I believe that if one exports an org file with sufficiently many empty
TODO headings (to me, it seems a perfectly valid use case of org,
printing lists of TODOs), they won't fit on a single page, and latex
will drop them. Would the latex snippet in this thread be a good
candidate for inclusion into org as a canned trick?
On Tue, 27 Aug 2019 at 14:57, Vladimir Nikishkin wrote:
I have indeed investigated the issue, and this is the link:
https://latex.org/forum/viewtopic.php?f=47=32788
To make the long story short, the folowing trick is needed to allow
page breaks after headings (which is a completely standard case in
-org).
#+begin_src latex
\usepackage{xpatch}
\makeatletter
% This is not recommended, because it can break several things
\xpatchcmd{\@afterheading}{\@nobreaktrue}{\@nobreakfalse}{%
\typeout{WARNING: \string\@afterheading\space broken}%
}{%
\@latexerr{ERROR: Cannot patch \string\@afterheading}\@ehd%
}
\makeatother
#+end_src
Shall this trick be considered for inclusion in 'org' officially?
I mean, having lists of empty headings is a perfectly standard use case for org.
What are the implications of doing this? In particular, the comment
% This is not recommended, because it can break several things
Many people have quite complex environments for generating Latex and we
would need to be certain that adding this package doesn't 'break several
things'.
For one thing, it allows something (La)TeX tries to circumvent: page
breaks immediately after a section heading. In normal documents, that's
something you want to avoid as much as possible.
Perhaps another approach would be more fitting, but it needs changing
the LaTeX output routine: Have org add something invisible after a
heading in case that heading's body is empty. That makes page breaks
possible (after that invisible something) without changing the behaviour
for non-empty sections.
Just my thoughts,
Julius Dittmar
[PATCH] doc/org-manual.org: add reference to org-table-transpose-table-at-point
Kyle, thanks. yes, blind copy and paste. i'm not a git-format-patch
expert, so let me know if this is the wrong format (i see some people
include inline, whereas others attach a file -- is one easier to handle
than the other?)
---
doc/org-manual.org | 5 +
1 file changed, 5 insertions(+)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 040fccc21..953ab6bd3 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -1649,6 +1649,11 @@ you, configure the option ~org-table-auto-blank-field~.
the buffer. You can activate this minor mode by default by setting
the option ~org-table-header-line-p~ to ~t~.
+- {{{kbd(M-x org-table-transpose-table-at-point)}}} ::
+
+ #+findex: org-table-transpose-table-at-point
+ Transpose the table at point and eliminate hlines.
+
** Column Width and Alignment
:PROPERTIES:
:DESCRIPTION: Overrule the automatic settings.
--
2.29.2
