[O] GTD and CRM workflow for org-mode using Agenda and org-super-agenda [followup]
I mentioned the setup I was recently using when I asked a question on how to "Add Notes" into a LOGBOOK property drawer (and thank you to the person who answered the question for me. It was a game-changer.). A surprising (to me, anyway) number of people asked me privately to follow up about my setup and how I was using thing, so I promised I would put a blog post together (I had a draft from march anyhow... =] ). Anyhow, have a solid draft up at: https://daryl.wakatara.com/a-better-gtd-and-crm-flow-for-emacs-org-mode Would love some feedback on if it answers peoples' question and would love some feedback on other things you'd need to see in it that it doesn't answer (within reason). ciao ! Daryl PS> I'm assuming I'm not violating any terms of use posting a blog post as it was topical.
Re: [O] [PATCH] Ruby tests
Hello, Achim Gratz writes: > Ruby tests have been failing for quite some time, here's my fix. Feel free to push these changes if they fix tests for you. Regards, -- Nicolas Goaziou
Re: [O] No LaTeX label when using :mode math #+NAME with table
Hello,
ed...@openmail.cc writes:
> I had to add :math-suffix to get a label in the exported TeX
> file (shown below), otherwise, there is no label. If I am the only one
> affected, disregard this message. I may not be able to answer in some
> days.
>
> #+NAME: tbl-arbitrary-factors
> #+CAPTION: Simplification of model parameters.
>
> #+ATTR_LATEX: :mode math :environment align* :math-suffix
> \label{tbl-arbitrary-factors}
> | a_{2} = \alpha\,10^{7} || , ||
> \frac{b_{2}}{3} = a_{2}|| , || \frac{d_{2}}{6.5}
> = a_{2} |
> | c_{2} = \beta\,10^{7}|| , ||
> g_{n} = \frac{g_{n}^{\max}}{1 + \beta} || , || g_{n}^{\max} =
> 0.55, 0.3, 0.15 |
> | k_{0}=\kappa\,\frac{10^{-9}}{\gamma_{\text{H}_{2}\text{O}}} || , ||
> \tau_{n} = \frac{\tau_{n}^{\max}}{1 + \kappa} || , || \tau_{n}^{\max} =
> 20, 100, 200 |
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Re: [O] Column width cookies stopped working in 9.2.3?
Neil Jerram writes: >> As Eric says, things have changed in this area. It's always a good >> idea to check the /etc/ORG-NEWS file for such things. In this >> particular case, read the section entitled "Dynamically narrow table >> columns" in the Version 9.2 "New features" section of etc/ORG-NEWS. > > Thanks Nick. I did check the manual before writing, and noticed that it > still says: > > To set the width of a column, one field anywhere in the column may > contain just the string ‘’ where N specifies the width as a number of > characters. Just to clarify: my intention was to advertise etc/ORG-NEWS more widely and point out that it's probably the best place to learn about things that are likely to break one's workflows (and if you read it before you update, you just might avoid unpleasant surprises - and this is not a specific "you", but a general "you" that includes everybody, including me: I often forget to do this and suffer the consequences). > > I think the crux of the matter is that my use case is apparently > different from everyone else's. Now that I've reread the whole > section, it seems that the main target use case is _shrinking_ a > column to be narrower than what is needed for its content. My use > case is the opposite: I want a column to be a fixed width that is > always _larger_ than its content. (FWIW, this is in order to > avoid spurious Git diffs for column width changes, as I change the > content in those tables.) > > For example, after deploying 'C-u C-c TAB', one of my tables now looks like > this: > > | Programme ...| Sang? ...| Notes ...| > |--...+---...+---...| > | Audition ...| ...| January 2019 ...| > |--...+---...+---...| > | <16> ...| <6> ...| <64> ...| > | 2019 ...| ...| ...| > | B minor mass ...| Yes ...| 1 planned absence (6 Mar) ...| > | ...| ...| 6 Mar Present when not expected ...| > | Songs Summer Eve ...| No ...| ...| > | French Choral ...| Yes ...| "I'm intending to sing in [this]" ...| > > which is IMO uglier than what it used to be, and what I'd like, like this: > > | Programme | Sang? | Notes > | > |--++--| > | Audition | | January 2019 > | > |--++--| > | <16> | <6> | <64> > | > | 2019 | | > | > | B minor mass | Yes | 1 planned absence (6 Mar) > | > | | | 6 Mar Present when not expected > | > | Songs Summer Eve | No | > | > | French Choral | Yes | "I'm intending to sing in [this]" > | > > Am I right about my use case being different, and therefore perhaps > having been caught up unintentionally in this change? > That may well be true: personally, I always thought of these cookies as minimum width specifiers, not maximum width. But I think you could do what you want by having a row that contains fixed width strings, instead of width cookies. To make it as unobtrusive as possible, I'd use non-breaking spaces as the character: | | | | | || | There may be better solutions, but this is what sprang to my mind after reading your use case. HTH -- Nick "There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." -Martin Fowler
Re: [O] LaTex Output with Index
On Sunday, 12 May 2019 at 10:17, Robert Love wrote:
> Can someone point to an example of using Org mode to generate a LaTeX
> document with an index? I see the Org has section 13.1.8 Generating
> an index. What is the means to turn that into LaTex with an index?
> Do I have to use a project? Is there a simple example?
That part of the manual is for publishing to HTML, not for creating a
PDF via LaTeX.
To generate an index for LaTeX, you add
#+index: term
lines to your org file.
You need to have a couple of extra bits in your org file for LaTeX to
know about creating an index. In particular, you need:
#+LaTeX_HEADER: \usepackage{makeidx} \makeindex
and then a \printindex statement somewhere in your org file (probably at
the end) for the index to be generated.
Once you have your org file the way you want it, you then need to use
LaTeX itself to create the index. So:
1. export to LaTeX
2. run pdflatex on the LaTeX file
3. run it again just to make sure (sometimes 3 runs are needed...)
4. then run makeindex on the file (base name)
5. finally run pdflatex again (maybe twice)
You can do all these steps from within Emacs. You can either visit the
LaTeX file directly to execute steps 2-5 or you can modify
org-latex-pdf-process (via file local variables, for instance) to insert
the makeindex command.
HTH.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2.3-327-g3375f0
[O] LaTex Output with Index
Can someone point to an example of using Org mode to generate a LaTeX document with an index? I see the Org has section 13.1.8 Generating an index. What is the means to turn that into LaTex with an index? Do I have to use a project? Is there a simple example?
[O] [PATCH] Ruby tests
Ruby tests have been failing for quite some time, here's my fix. >From 2f1bbaab939f6b6ceceb72862470e0576a8e2cba Mon Sep 17 00:00:00 2001 From: Achim Gratz Date: Sun, 12 May 2019 13:14:04 +0200 Subject: [PATCH 1/1] test-ob-ruby.el: fix tests * testing/lisp/test-ob-ruby.el: Output no longer contains a trailing newline, remove from the template to compare against. Session must be named for the tests to actually work, also add some extra code to ascertain that the code after the output statement has actually run in the session. --- testing/lisp/test-ob-ruby.el | 25 + 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/testing/lisp/test-ob-ruby.el b/testing/lisp/test-ob-ruby.el index f42987b639..4d676fe19a 100644 --- a/testing/lisp/test-ob-ruby.el +++ b/testing/lisp/test-ob-ruby.el @@ -22,57 +22,58 @@ (signal 'missing-test-dependency "Support for Ruby code blocks")) (ert-deftest test-ob-ruby/session-output-1 () -(should (equal (org-test-with-temp-text "#+begin_src ruby :session :results output +(should (equal (org-test-with-temp-text "#+begin_src ruby :session org-test-ruby :results output s = \"1\" s = \"2\" s = \"3\" puts s +s = \"4\" #+end_src" (org-babel-execute-maybe) (substring-no-properties (buffer-string))) - "#+begin_src ruby :session :results output + "#+begin_src ruby :session org-test-ruby :results output s = \"1\" s = \"2\" s = \"3\" puts s +s = \"4\" #+end_src #+RESULTS: : 3 - "))) (ert-deftest test-ob-ruby/session-output-2 () -(should (equal (org-test-with-temp-text "#+begin_src ruby :session :results output -s = \"5\" +(should (equal (org-test-with-temp-text "#+begin_src ruby :session org-test-ruby :results output puts s +s = \"5\" #+end_src" (org-babel-execute-maybe) (substring-no-properties (buffer-string))) - "#+begin_src ruby :session :results output -s = \"5\" + "#+begin_src ruby :session org-test-ruby :results output puts s +s = \"5\" #+end_src #+RESULTS: -: 5 - +: 4 "))) (ert-deftest test-ob-ruby/session-output-3 () -(should (equal (org-test-with-temp-text "#+begin_src ruby :session :results output +(should (equal (org-test-with-temp-text "#+begin_src ruby :session org-test-ruby :results output puts s +s = \"6\" #+end_src" (org-babel-execute-maybe) (substring-no-properties (buffer-string))) - "#+begin_src ruby :session :results output + "#+begin_src ruby :session org-test-ruby :results output puts s +s = \"6\" #+end_src #+RESULTS: : 5 - "))) (provide 'test-ob-ruby) -- 2.21.0 Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Column width cookies stopped working in 9.2.3?
On Sun, 12 May 2019 at 00:29, Nick Dokos wrote: > > Neil Jerram writes: > > > Hi, > > > > I have tables with width cookies like this: > > > > | <16> | <6> | <64> | > > > > I just added new information to one of those tables, and the table > > shrank down to match the size of the content, i.e. as though Org is > > now ignoring the width cookies. > > > > I believe I've also upgraded in the last few days, and now have: > > Org mode version 9.2.3 (9.2.3-13-g727c3f-elpa @ > > /home/neil/.emacs.d/elpa/org-20190506/) > > > > Is this a known thing? Do I need something else now to make those > > width cookies work? > > > > As Eric says, things have changed in this area. It's always a good > idea to check the /etc/ORG-NEWS file for such things. In this > particular case, read the section entitled "Dynamically narrow table > columns" in the Version 9.2 "New features" section of etc/ORG-NEWS. Thanks Nick. I did check the manual before writing, and noticed that it still says: To set the width of a column, one field anywhere in the column may contain just the string ‘’ where N specifies the width as a number of characters. I think the crux of the matter is that my use case is apparently different from everyone else's. Now that I've reread the whole section, it seems that the main target use case is _shrinking_ a column to be narrower than what is needed for its content. My use case is the opposite: I want a column to be a fixed width that is always _larger_ than its content. (FWIW, this is in order to avoid spurious Git diffs for column width changes, as I change the content in those tables.) For example, after deploying 'C-u C-c TAB', one of my tables now looks like this: | Programme...| Sang? ...| Notes ...| |--...+---...+---...| | Audition ...| ...| January 2019 ...| |--...+---...+---...| | <16> ...| <6> ...| <64> ...| | 2019 ...| ...| ...| | B minor mass ...| Yes ...| 1 planned absence (6 Mar) ...| | ...| ...| 6 Mar Present when not expected ...| | Songs Summer Eve ...| No...| ...| | French Choral...| Yes ...| "I'm intending to sing in [this]" ...| which is IMO uglier than what it used to be, and what I'd like, like this: | Programme| Sang? | Notes | |--++--| | Audition || January 2019 | |--++--| | <16> | <6>| <64> | | 2019 || | | B minor mass | Yes| 1 planned absence (6 Mar) | | || 6 Mar Present when not expected | | Songs Summer Eve | No | | | French Choral| Yes| "I'm intending to sing in [this]" | Am I right about my use case being different, and therefore perhaps having been caught up unintentionally in this change? Best wishes, Neil
