Re: [O] how to prevent long lines being cut when exporting from org to pdf
On Monday, 8 Dec 2014 at 20:16, Suhas Pai wrote:
> Hi Eric,
> Yes, there has to be physical limits to the length of line. I was
> hopingto play with the font size to shrink the line in some cases. Is
> there one?This is at the cost of testing the limits of what you can
> read without needinga magnifying glass.
You could try
,
| #+latex: {\fotnotesize
| ...
| #+latex: }
`
Check out a LaTeX manual for the various sizes available.
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-595-g5945be
Re: [O] Warning about section named "Footnotes"
Arni Magnusson writes: > I have revised the paragraph following your suggestion, and prepared > the patch using the 'git format-patch' command. See below. Thank you. However, I'm unable to apply it. Could you try to update Org first and send it again as an attachment? Also, you need to specify the node modified in the commit message. > In the past, I have signed FSF papers for Emacs and Texinfo > contributions. Does that cover this contribution as well? If not, I'm > happy with the TINYCHANGE stamp. The stamp is not needed, then. Regards,
Re: [O] Mistake in org-mode manual
Amitai Hoze writes: > Hi, sorry, I opened the page and the mistake is still there. The page may take some time to be updated. However, the texi manual is fixed. Regards,
Re: [O] html export does seem to no more recognise EXPORT_ .. PROPERTIES
Rainer Stengele writes: > The only thing that is different from the past is that any "comment" in the > PROPERTIES section does seem to confuse the exporter. > I removed > > :PROPERTIES: > :EXPORT_FILE_NAME: > x:/0PROJEKT/Kunden/customer/customer-Dokumentation-mmdd.html > EXPORT_FILE_NAME: > x:/0PROJEKT/Kunden/customer/customer-Dokumentation-another-title.html > :EXPORT_TITLE: Stoll - IT (HW/SW) - Zugänge - Konfigurationen [Stand: > mmdd] > :END: > > As an example I removed the second line in the :PROPERTIES: block and > the standard html export does respect the file name again. Org syntax is much less tolerant wrt property drawers now: they can only contain node properties. Regards,
Re: [O] [RFC/PATCH] Fixes for org-timer
Kyle Meyer writes: > I've attached updated patches. Applied (with a minor change in `org-timer--get-timer-title'). Thank you. Regards,
[O] [RFC/PATCH] Adding org-babel support for rust (ob-rust.el)
Dear org-mode developers I've been working on adding support for rust in org-babel, and this is what I've come up with so far. It's basically just a modification of ob-C.el. The branch is viewable at [0], but so far the only commit is [1]. I've also attached an example of how it works. Note that you will need rustc to run the examples, and that I've only tested them with rust 0.12 and the latest from git. I'm very interested in getting this merged into org-mode, as I imagine other rust developers are, so please let me know what I can do to help, for example if you require tests or other forms of documentation. Kind regards Philip Munksgaard 0: https://github.com/Munksgaard/org-mode/tree/ob-rust 1: https://github.com/Munksgaard/org-mode/commit/a6ffbb0120a2313464c621f80db93e2475ac25ac ob-rust.org Description: Lotus Organizer
Re: [O] Org-todo-yesterday broken?
Hello, Kyle Meyer writes: > I'd guess this is because org-use-effective-time is set to nil (based on > this previous issue [1]). Setting it to non-nil should work, but I > think org-todo-yesterday and org-agenda-todo-yesterday should override > this, as in the attached patch. Applied. Thank you. Regards, -- Nicolas Goaziou
Re: [O] problems with INCLUDE, noweb and tangle
Hello, Daniele Pizzolli writes: > The noweb reference in the included file is not present in tangle (and > sometimes also is not present within the results in the buffer). File inclusion, through INCLUDE keywords, is an export-only feature. Regards, -- Nicolas Goaziou
Re: [O] how to prevent long lines being cut when exporting from org to pdf
On Tuesday, 9 Dec 2014 at 07:39, Eric S Fraga wrote:
[...]
> You could try
>
> ,
> | #+latex: {\fotnotesize
Ooops, that should have been \footnotesize.
A list of possible sizes can be found here:
https://engineering.purdue.edu/ECN/Support/KB/Docs/LaTeXChangingTheFont
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-589-g9eff31.dirty
Re: [O] Dependency on gnus?
Rasmus gmx.us> writes: > > Hi, > > Thibaut Verron gmail.com> writes: > > > After installing the latest snapshot of orgmode (20141208 or 8.2.10-23), it > > fails loading, stating that gnus is not provided. Commenting out the > > "(require 'gnus-sum)" line in org.el seems to fix it (I mean that at least > > it loads). > > You should already have Gnus. It comes with Emacs. Did you do something > to actively remove it? > Ok, figured it out. Never tried to remove it, but I tried to use it once. During this, I created a file named "gnus.el" supposed to hold my config, and (this shouldn't have happened) dropped it in my load-path instead of the folder where all my config files are. Nevermind, sorry. And thanks for the help! Thibaut
Re: [O] problems with INCLUDE, noweb and tangle
Hello Nicolas, Nicolas Goaziou writes: > Hello, > > Daniele Pizzolli writes: > >> The noweb reference in the included file is not present in tangle (and >> sometimes also is not present within the results in the buffer). > > File inclusion, through INCLUDE keywords, is an export-only feature. Thanks for the clarification. I did not noticed that before. I guess that there is no plan to get this working for the general case, so the only viable option is using one big .org file. Best, Daniele
Re: [O] [PATCH] org-src: allow `org-babel-edit-prep:.*' to mark region
Hi Nicolas, >> Well, I'm not trying to push my markup or anything, I just want my >> custom `org-babel-edit-prep:elisp' to be able to mark the region. >> Currently I'm not given that option. > > Understood. > > Would you mind providing a patch with format-patch, and reference the > current thread in the commit message? I can just push it through if you don't mind. I have push access. Is this OK as reference: http://article.gmane.org/gmane.emacs.orgmode/93053 ? regards, Oleh
Re: [O] problems with INCLUDE, noweb and tangle
Daniele Pizzolli wrote: > Hello Nicolas, > > Nicolas Goaziou writes: > >> Hello, >> >> Daniele Pizzolli writes: >> >>> The noweb reference in the included file is not present in tangle (and >>> sometimes also is not present within the results in the buffer). >> >> File inclusion, through INCLUDE keywords, is an export-only feature. > > Thanks for the clarification. I did not noticed that before. I guess > that there is no plan to get this working for the general case, so the > only viable option is using one big .org file. Or use the Library of Babel, if the code you wanna tangle gets eventually used in many different files? ┌ │ 14.6 Library of Babel │ = │ │ The “Library of Babel” consists of code blocks that can be called from │ any Org mode file. Code blocks defined in the “Library of Babel” can be │ called remotely as if they were in the current Org mode buffer (see │ *note Evaluating code blocks:: for information on the syntax of remote │ code block evaluation). │ │The central repository of code blocks in the “Library of Babel” is │ housed in an Org mode file located in the ‘contrib’ directory of Org │ mode. │ │Users can add code blocks they believe to be generally useful to │ their “Library of Babel.” The code blocks can be stored in any Org mode │ file and then loaded into the library with ‘org-babel-lob-ingest’. │ │Code blocks located in any Org mode file can be loaded into the │ “Library of Babel” with the ‘org-babel-lob-ingest’ function, bound to │ ‘C-c C-v i’. └ Best regards, Seb -- Sebastien Vauban
[O] [bug, patch, ox] INCLUDE and footnotes
Hi,
When using LINES in `org-export--prepare-file-contents' the footnotes
section is not preserved causing export to fail.
Minimal example
$> cat t{1,2}.org
# this is t1.org
* intro
foo[fn:1]
* sec2
bar
* Footnotes
[fn:1] baz
# this is t2.org
#+INCLUDE: "./t1.org::#intro"
And export t2.org.
The attached patch fixes this by explicitly saving the footnote section
(Aside: org-footnote-section is used in hackish ways; should we make a
function that returns to correct regexp for the footnotes section?).
It works in a rather large document of mine and in the minimal test.
Should I apply it, or is there a better way to fix this bug?
Thanks,
Rasmus
--
Slowly unravels in a ball of yarn and the devil collects it
>From 3f352159d9011e6a00af853fa6dadb04a5b46c87 Mon Sep 17 00:00:00 2001
From: rasmus
Date: Tue, 9 Dec 2014 12:40:52 +0100
Subject: [PATCH] ox.el: Fix footnote-bug in #+INCLUDE-keyword
* ox.el (org-export--prepare-file-contents): Preserve footnote-section
when using the LINES argument.
---
lisp/ox.el | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/lisp/ox.el b/lisp/ox.el
index 9d9e794..8d4fd6c 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -3260,8 +3260,22 @@ with footnotes is included in a document."
(end (if (zerop lend) (point-max)
(goto-char (point-min))
(forward-line (1- lend))
- (point
- (narrow-to-region beg end)))
+ (point)))
+ (footnote-section
+ (save-excursion
+ (goto-char (point-min))
+ (when (search-forward-regexp
+ (concat "^\\*+[ \t]+" org-footnote-section "[ \t]*$")
+ nil t)
+ (buffer-substring
+ (point-at-bol)
+ (or
+ (and (search-forward-regexp org-heading-regexp nil t)
+ (point-at-bol))
+ (point-max)))
+ (narrow-to-region beg end)
+ (and footnote-section
+ (insert "\n" footnote-section
;; Remove blank lines at beginning and end of contents. The logic
;; behind that removal is that blank lines around include keyword
;; override blank lines in included file.
--
2.1.3
Re: [O] problems with INCLUDE, noweb and tangle
Hello Sebastien, Sebastien Vauban writes: >> Thanks for the clarification. I did not noticed that before. I guess >> that there is no plan to get this working for the general case, so the >> only viable option is using one big .org file. > > Or use the Library of Babel, if the code you wanna tangle gets > eventually used in many different files? Thanks, I was not aware of this option. But it seems that the blocks are statically added to the variable org-babel-library-of-babel, so when I change the included files the changes does not propagate to the library of babel automatically. I also prefer a file based solution rather than a global one. Best, Daniele
Re: [O] problems with INCLUDE, noweb and tangle
Daniele Pizzolli wrote: > Sebastien Vauban writes: > >>> Thanks for the clarification. I did not noticed that before. I guess >>> that there is no plan to get this working for the general case, so the >>> only viable option is using one big .org file. >> >> Or use the Library of Babel, if the code you wanna tangle gets >> eventually used in many different files? > > Thanks, I was not aware of this option. But it seems that the blocks > are statically added to the variable org-babel-library-of-babel, so when > I change the included files the changes does not propagate to the > library of babel automatically. I also prefer a file based solution > rather than a global one. The idea of the LOB is that it's a place where you put all the code blocks you use in more than one file; you load the LOB, and the code blocks are in memory -- known, so that you can reference them. If you need to update them, the easiest is to directly edit them in (one of) the (many) LOB file(s). Best regards, Seb -- Sebastien Vauban
Re: [O] html export does seem to no more recognise EXPORT_ .. PROPERTIES
Am 09.12.2014 um 09:58 schrieb Nicolas Goaziou: > Rainer Stengele writes: > >> The only thing that is different from the past is that any "comment" in the >> PROPERTIES section does seem to confuse the exporter. >> I removed >> >> :PROPERTIES: >> :EXPORT_FILE_NAME: >> x:/0PROJEKT/Kunden/customer/customer-Dokumentation-mmdd.html >> EXPORT_FILE_NAME: >> x:/0PROJEKT/Kunden/customer/customer-Dokumentation-another-title.html >> :EXPORT_TITLE: Stoll - IT (HW/SW) - Zugänge - Konfigurationen [Stand: >> mmdd] >> :END: >> >> As an example I removed the second line in the :PROPERTIES: block and >> the standard html export does respect the file name again. > > Org syntax is much less tolerant wrt property drawers now: they can only > contain node properties. > > > Regards, > > Good to know and reasonable. I am glad the simple (non publishing) functionality did not disappear. I found another strange thing: I do start my Org files with a headline. If the :PROPERTIES: block follows after a blank line the settings are not observed for the subtree. If I delete that empty line it works (filename path is observed). I wonder if this is intended? If yes it could confuse users of such a properties block, thinking it works for the related subtree no matter if empty lines are there or not. Thank you. Regards, Rainer
Re: [O] relative deadlines
On Tue, Dec 09, 2014 at 10:36:52AM +0100, Nicolas Goaziou wrote: > Hello, > > Jeffrey Brent McBeth writes: > > > I have a python function that can take a stripped down org file and > > places an active date after each ## (or inactive after > > #[block]#), that I hacked up today to see if it would really be as > > useful as I thought, but I keep thinking that someone somewhere must > > have scratched this itch elsewhere, and having to partially parse org > > in python and modify the text rather than having my agenda smart > > enough to figure it out gives me pause... > > It sounds like over-engineering to me. I very well may be. A common fault of engineers :) > I think it would be better to have a function shifting all timestamps in > a subtree. It may even exist already. I cannot remember. This is where I fall down. I don't see how that meets my basic need case. I know that certain sub tasks need to start 90 days before the final deadline (for example), I can hand count back 90 days and then do the shifting of timestamps, but then the core relevant information is lost of -90d. I have a strong feeling that since my searches don't turn things up, that this is a weird way in which I work rather than the rest of the subcommunity here; so I do appreciate the kind feedback above, I am not yet convinced that I'm insane :) > > If nobody have better ideas, are the block delimiters I'm using going > > to conflict with some other feature in org that I'm just not using > > yet? > > I don't think so. That is helpful. I read through your wonderful syntax file looking for decent delimeters that wouldn't be a pain to type, and I'm glad that there are no obvious howlers for me. Jeff -- "The man who does not read good books has no advantage over the man who cannot read them." -- Mark Twain
Re: [O] relative deadlines
Jeffrey Brent McBeth writes: > This is where I fall down. I don't see how that meets my basic need > case. If you want to repeat the main task and sub-tasks, the function will preserve difference between the timestamps. > I know that certain sub tasks need to start 90 days before the final > deadline (for example), I can hand count back 90 days and then do the > shifting of timestamps, but then the core relevant information is lost > of -90d. You can also modify (advice) `org-deadline' and `org-scheduled' so their base value is the one above in the subtree instead of current date. Another option is to add a keymap to `org-read-date-minibuffer-local-map' that would set the base date to the last one computed. You could then choose your date incrementally (e.g., first move to the deadline date of the task, then backwards 90 days with -90d). I'm unsure about the net benefit, tho. Regards,
Re: [O] html export does seem to no more recognise EXPORT_ .. PROPERTIES
Rainer Stengele writes: > I do start my Org files with a headline. If the :PROPERTIES: block follows > after a blank line the settings are not observed for the subtree. > If I delete that empty line it works (filename path is observed). > I wonder if this is intended? It is. Properties drawers have now a very specific location in a section, much line planning info line. > If yes it could confuse users of such a properties block, thinking it > works for the related subtree no matter if empty lines are there or > not. Users are already accustomed to planning info lines, which work the same way. Regards,
Re: [O] [PATCH] org-src: allow `org-babel-edit-prep:.*' to mark region
Oleh writes: >> Would you mind providing a patch with format-patch, and reference the >> current thread in the commit message? > > I can just push it through if you don't mind. I have push access. Sure, go ahead. Thank you. > Is this OK as reference: > http://article.gmane.org/gmane.emacs.orgmode/93053 ? It is. Regards,
Re: [O] how to prevent long lines being cut when exporting from org to pdf
Hi Eric,
I can't thank you enough. Your suggestion of changing the font sizeworked
great. The die-hard inquisitive would need a magnifying glassbut the
information is there. I guess there is no wrap-around feature forlong lines.
Thanks again!
Suhas
From: Eric S Fraga
To: Suhas Pai
Cc: "emacs-orgmode@gnu.org"
Sent: Tuesday, December 9, 2014 1:46 AM
Subject: Re: [O] how to prevent long lines being cut when exporting from org
to pdf
On Tuesday, 9 Dec 2014 at 07:39, Eric S Fraga wrote:
[...]
> You could try
>
> ,
> | #+latex: {\fotnotesize
Ooops, that should have been \footnotesize.
A list of possible sizes can be found here:
https://engineering.purdue.edu/ECN/Support/KB/Docs/LaTeXChangingTheFont
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-589-g9eff31.dirty
Re: [O] relative deadlines
Jeffrey Brent McBeth writes: > From time to time (each time I delve into using org-mode for deadlines > before my habits fall apart), I find the desire to have some form of > relative deadlines. By this I mean, that there are often sequences of > tasks that I know the time required to complete and when things are > due. These tasks may repeat (usually do). > > It would be awful helpful to me, but I would guess few others, as a > search didn't find much, for there to be some annotation like this > (example is farcical, notation is notional) > > * Go on date > DEADLINE: <2014-12-25> > ** Ask Girl #<-3w># > ** Wash Hair #<-2w># > ** Make Money #<-1w2d># > ** Get in Car #<-0d># > ** Call her back #<+1w># > > that in the agenda view would show as a sequence of tasks with the following > dates > Go on date <2014-12-25> > Ask Girl <2014-12-04> > Wash Hair <2014-12-11> > Make Money <2014-12-16> > Get in Car <2014-12-25> > Call her back <2015-01-01> > > I have a python function that can take a stripped down org file and > places an active date after each ## (or inactive after > #[block]#), that I hacked up today to see if it would really be as > useful as I thought, but I keep thinking that someone somewhere must > have scratched this itch elsewhere, and having to partially parse org > in python and modify the text rather than having my agenda smart > enough to figure it out gives me pause... > > If nobody have better ideas, are the block delimiters I'm using going > to conflict with some other feature in org that I'm just not using > yet? > > The main functuionality I'm stumbling toward is having an easily > moveable end date (so replacing the block with absolute dates is a > nono). > > Thanks for your attention, > Jeffrey McBeth I think like that as well. I know when some _thing_ has to be done. Then I start thinking of all the support items in relative terms to the main one. You should add this to org mode, if able. It would be a nice addition... Dave
Re: [O] table formula help...
Le 09/12/2014 06:54, Michael Brand a écrit : > Hi Thierry > > On Mon, Dec 8, 2014 at 10:57 PM, Thierry Banel wrote: >> You instantly found the weakness of the current design! > The reason follows very shortly. ;-) > >> Definitely interesting. Someone else has already bumped into the empty >> cells thing. > It was me: > http://thread.gmane.org/gmane.emacs.orgmode/63559/focus=63975 > > Michael > Excellent. With your help, the aggregate package will reach the next level.
Re: [O] [dev] New version of org-index.el --- a personal index for org and beyond
Hello,
On 2014-12-08 22:00, Marc Ihm writes:
> Hi all,
>
> the new version 3.0.0 of org-index.el has been uploaded to the
> contrib-directory of orgs git-repository.
>
> Features include improved setup-assistant and the new command "add",
> which adds the current node to your index.
> Moreover the structure of the index-table and its flags has been
> reworked (hence the increment in major version number).
I've given it a try, and upon creation there is a backtrace (when I'm
done with the setup):
Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
org-index--goto-list("columns-and-flags")
org-index--create-index()
org-index--create-missing-index("Variable org-index-id is not set, so
probably no index table has been created yet.")
org-index--verify-id()
org-index(nil)
call-interactively(org-index record-it)
The table seems to be created, so I guess it's just a single occurrence
of a setup error.
Best,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
signature.asc
Description: PGP signature
Re: [O] table formula help...
Le 08/12/2014 19:02, Michael Brand a écrit : > #+TBLNAME: original > | Item | Value | > |--+---| > | a2 | 1 | > | a2 | 1 | > | a0 |-1 | > | a0 | 1 | > | b2 | 2 | > | b2 | | > | b0 | 0 | > | b0 | | > | c| | > | c| | > > #+BEGIN: aggregate :table original :cols "Item sum(Value) mean(Value)" > | Item | sum(Value) | mean(Value) | > |--++-| > | a2 | 2 | 1 | > | a0 || | > | b2 | 2 | 1 | > | b0 || | > | c|| | > #+END > > Could you please add this example or something in the same sense to > the unittests.org before any other change? > Done under the title "* Test zero output". There is also a new "* Test empty inputs" were several empty input cases are tested against all the available aggregations (sum, mean, max, corr, and so on). I will work on a new and clean design for handling empty inputs. It shouldn't be so difficult after all. Stay tuned. Have fun Thierry
Re: [O] [bug, patch, ox] INCLUDE and footnotes
Rasmus writes:
> The attached patch fixes this by explicitly saving the footnote section
As per usual my first patch is dodgy. It occurred to me that Org can
handle several footnote sections (that's how #+INCLUDE supports footnotes,
I guess). The attached patch how supports export of t2.org in this
example
$> cat t{1,2}.org
# this is t1.org
* foo
bar[fn:1]
baz[fn:2]
* Footnotes
[fn:1] bar.corp
* Footnotes
[fn:2] baz.corp
# this is t2.org
#+INCLUDE: "/tmp/t1.org::*foo"
However, there is a pitch-fall when doing
#+INCLUDE: "/tmp/t1.org::*foo0"
#+INCLUDE: "/tmp/t1.org::*foo1"
Now *foo1 will be inserted under the footnote-heading of *foo0 which means
it won't be exported. If min-level is used this is not an issue of
course, but that's kind of unexpected (so is the fact that the second
include will become a child of the first include, but that's another
patch) .
Perhaps a better overall approach (if the above limitation is
unacceptable) would to translate all footnotes in an INCLUDEd file to
inline ones, e.g. when including * foo in t1.org above, what would be
inserted is
* foo
bar[fn::bar.corp]
baz[fn::baz.corp]
Yet another solution would be to return a cond of
(included-text . included-footnotes)
and make sure to insert footnotes at the very end.
WDYT?
—Rasmus
--
. . . The proofs are technical in nature and provides no real understanding
>From 2a943b40c024df092cc2cf020bdf2646e7ab4b2c Mon Sep 17 00:00:00 2001
From: rasmus
Date: Tue, 9 Dec 2014 12:40:52 +0100
Subject: [PATCH] ox.el: Fix footnote-bug in #+INCLUDE-keyword
* ox.el (org-export--prepare-file-contents): Preserve footnote-section
when using the LINES argument.
---
lisp/ox.el | 23 +--
1 file changed, 21 insertions(+), 2 deletions(-)
diff --git a/lisp/ox.el b/lisp/ox.el
index 9d9e794..bf2ce4d 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -3260,8 +3260,27 @@ with footnotes is included in a document."
(end (if (zerop lend) (point-max)
(goto-char (point-min))
(forward-line (1- lend))
- (point
- (narrow-to-region beg end)))
+ (point)))
+ (footnote-section-re
+ (concat "^\\*+[ \t]+" org-footnote-section "[ \t]*$"))
+ (footnote-sections
+ (save-match-data
+ (save-excursion
+ (goto-char (point-min))
+ (loop do
+ (or (search-forward-regexp footnote-section-re nil t)
+ (end-of-buffer))
+ while (not (eobp))
+ collect
+ (buffer-substring
+ (line-beginning-position)
+ (or (and
+ (search-forward-regexp org-heading-regexp nil t)
+ (goto-char (match-beginning 0)))
+ (point-max
+ (narrow-to-region beg end)
+ (and footnote-sections
+ (insert "\n" (mapconcat 'identity footnote-sections "\n")
;; Remove blank lines at beginning and end of contents. The logic
;; behind that removal is that blank lines around include keyword
;; override blank lines in included file.
--
2.1.3
Re: [O] [bug, patch, ox] INCLUDE and footnotes
Hello,
Rasmus writes:
> When using LINES in `org-export--prepare-file-contents' the footnotes
> section is not preserved causing export to fail.
>
> Minimal example
>
> $> cat t{1,2}.org
> # this is t1.org
> * intro
> foo[fn:1]
> * sec2
> bar
> * Footnotes
>
> [fn:1] baz
>
>
> # this is t2.org
> #+INCLUDE: "./t1.org::#intro"
>
> And export t2.org.
>
> The attached patch fixes this by explicitly saving the footnote section
>
> (Aside: org-footnote-section is used in hackish ways; should we make a
> function that returns to correct regexp for the footnotes section?).
>
> It works in a rather large document of mine and in the minimal test.
>
> Should I apply it, or is there a better way to fix this bug?
Thanks for the patch. However, it is incorrect.
First `org-footnote-section' could be nil, in which case there is no
headline to look after.
Also, there may be multiple footnote sections in the included document,
or even some footnote definitions inside and some outside the single
section...
Eventually, you are inserting a headline in the source document, which
could break its structure (e.g., if you're only inserting a table).
You should only extract the definitions associated to the references
within the included part of the document. However, you cannot insert
them right after the included text, as it could break the surrounding
environment, e.g.,
- item
#+INCLUDE: some-table.org
A possible solution would be to somehow postpone insertion of footnotes
at the very end of the source document, not at the location of the
keyword. However it would need some testing.
Regards,
--
Nicolas Goaziou
Re: [O] [dev] New version of org-index.el --- a personal index for org and beyond
On 2014-12-09 19:58, Alan Schmitt writes:
> I've given it a try, and upon creation there is a backtrace (when I'm
> done with the setup):
>
> Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
> org-index--goto-list("columns-and-flags")
> org-index--create-index()
> org-index--create-missing-index("Variable org-index-id is not set,
> so probably no index table has been created yet.")
> org-index--verify-id()
> org-index(nil)
> call-interactively(org-index record-it)
>
> The table seems to be created, so I guess it's just a single occurrence
> of a setup error.
As a followup, org-index could not find the id after restarting emacs,
so I guess the backtrace happened before it was saved. I manually added
the `org-index-id' to my .emacs and it now works.
I tried adding a node, and although I changed the category and keyword
that were proposed to me, the node was inserted with the default ones.
Is this the place to report such bugs?
Thanks,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
signature.asc
Description: PGP signature
[O] Inserting property drawers and comments
Hi, I can insert a property drawer using the 'C-u C-c C-x d' key sequence. Is there a way to do so by directly calling the org-insert-property-drawer function? I get a 'Wrong type argument: commandp, org-insert-property drawer error' when I try to call it using a shortcut command. I have a similar problem with org-insert-comment and org-insert-item, but others like org-insert-link, org-insert-todo-heading, etc work fine. Thanks RC
[O] Tag filter inheritence
When I filter by tag (C-c / m) for, say, @internet, the tag for the parent also shows up (which might have a different tag, say, @errands). Is there any way to see _only_ tags that have @internet and filter out tags inherited from the parent?
Re: [O] Inserting property drawers and comments
You probably need to specify arguments, which can’t be done with M-x Try M-: ( …) From: emacs-orgmode-bounces+subhant=familycareinc@gnu.org [mailto:emacs-orgmode-bounces+subhant=familycareinc@gnu.org] On Behalf Of RCY Sent: Tuesday, December 09, 2014 12:40 PM To: Emacs-orgmode@gnu.org Subject: [O] Inserting property drawers and comments Hi, I can insert a property drawer using the 'C-u C-c C-x d' key sequence. Is there a way to do so by directly calling the org-insert-property-drawer function? I get a 'Wrong type argument: commandp, org-insert-property drawer error' when I try to call it using a shortcut command. I have a similar problem with org-insert-comment and org-insert-item, but others like org-insert-link, org-insert-todo-heading, etc work fine. Thanks RC This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message. Thank you.
Re: [O] [PATCH] WAS Re: Bug: problem w/ R code blocks [8.3beta (release_8.3beta-362-ga92789 /usr/local/share/emacs/site-lisp/org/)]
Hi, On this old subject, I too finally confirm the pushed patch addresses the issue - and - thanks. >-Original Message- >From: emacs-orgmode-bounces+mec=stowers@gnu.org >[mailto:emacs-orgmode-bounces+mec=stowers@gnu.org] On >Behalf Of Aaron Ecay >Sent: Friday, October 10, 2014 11:37 AM >To: Henrik Singmann; emacs-orgmode@gnu.org >Subject: Re: [O] [PATCH] WAS Re: Bug: problem w/ R code blocks [8.3beta >(release_8.3beta-362-ga92789 >/usr/local/share/emacs/site-lisp/org/)] > >Hi Henrik, > >2014ko urriak 10an, Henrik Singmann-ek idatzi zuen: >> >> Hi Aaron, >> >> This patch also solves the problem for me. No more ".ess.eval" not >> found! > >Thanks for testing. I’ve pushed the patch to the master branch. > >-- >Aaron Ecay
Re: [O] Inserting property drawers and comments
RCY wrote: > I can insert a property drawer using the 'C-u C-c C-x d' key > sequence. Is there a way to do so by directly calling the > org-insert-property-drawer function? I get a 'Wrong type argument: > commandp, org-insert-property drawer error' when I try to call it > using a shortcut command. It's not an interactive function. If you prefer to bind it directly to a key, you can wrap it in a command and then bind that to a key. (defun my/org-insert-property-draw () (interactive) (org-insert-property-drawer)) -- Kyle
Re: [O] [bug, patch, ox] INCLUDE and footnotes
Hi,
Nicolas Goaziou writes:
> First `org-footnote-section' could be nil, in which case there is no
> headline to look after.
Sure.
> Also, there may be multiple footnote sections in the included document,
> or even some footnote definitions inside and some outside the single
> section...
Multiple footnote sections are supported in the second revision of the
patch...
> You should only extract the definitions associated to the references
> within the included part of the document. However, you cannot insert
> them right after the included text, as it could break the surrounding
> environment, e.g.,
>
> - item
>
> #+INCLUDE: some-table.org
>
> A possible solution would be to somehow postpone insertion of footnotes
> at the very end of the source document, not at the location of the
> keyword. However it would need some testing.
Right, I note something similar in my second post.
http://permalink.gmane.org/gmane.emacs.orgmode/93299
Clearly the current situation is not satisfactory ("You can use :lines,
but only if no footnotes are present. . . IOW, :lines supports a subset
of Org syntax.").
I prefer converting [fn:N] references to [fn::FOOTNOTE] (see my other
email). Any obvious downsides?
—Rasmus
--
Vote for proprietary math!
Re: [O] Inserting property drawers and comments
Kyle Meyer kyleam.com> writes: > It's not an interactive function. If you prefer to bind it directly to > a key, you can wrap it in a command and then bind that to a key. > > (defun my/org-insert-property-draw () > (interactive) > (org-insert-property-drawer)) > Thanks! That worked.
Re: [O] CLOCKSUM counts appointments excluded by tag
I made a mistake in my first mail: the totals are for the Effort property
not CLOCKSUM.
Can no one confirm this? Is there something else wrong with my post? The
situation is the same after pulling from master today.
On 4 December 2014 at 22:58, Myles English wrote:
> Hello,
>
> I am using git master from yesterday (commit 6d2a661f) and have found
> that when the agenda is narrowed by tag (i.e. all appointments marked
> with a certain tag are excluded), the clocksum still shows the
> un-narrowed total. Is this the correct behaviour, or a bug?
>
> Selected variables:
>
> org-agenda-columns-add-appointments-to-effort-sum is t
> org-columns-default-format:
> "%80ITEM(Task) %10Effort(Effort){:} %10Duration(Duration){:} %10CLOCKSUM"
>
> org-global-properties:
> (("Effort_ALL" . "0:00 0:10 0:30 1:00 2:00 3:00 4:00 5:00 6:00 7:00 8:00
> 16:00 24:00 32:00"))
>
> Test org file:
>
>
> ;;,--
> ;;| * Nail org mode bug
> ;;| SCHEDULED: <2014-12-04 Thu 9:00-10:00>
> ;;|
> ;;| * Earn money
> :spouse:
> ;;| SCHEDULED: <2014-12-04 Thu 09:00-20:00>
> ;;|
> ;;| * Drink tea
> ;;| SCHEDULED: <2014-12-04 Thu 10:00-16:00>
>
> ;;`--
>
>
> C-c a < a ;; get the agenda for the current test file
> C-c C-x C-c ;; turn on column view
>
> ;;,--
> ;;| Thursday4 December 2014 | 18:00 |
> ;;|8:00..
> ;;| * Nail org mode bug | 1:00 |
> ;;| * Earn money| 11:00 |
> ;;| * Drink tea | 6:00 |
> ;;`--
>
>
> / - TAB 'spouse' ;; narrow by excluding the item tagged 'spouse'
>
> See how the 18:00 has counted the 11:00 that should have been excluded:
>
> ;;,--
> ;;| Thursday4 December 2014 | 18:00 |
> ;;|8:00..
> ;;| * Nail org mode bug | 1:00 |
> ;;| * Drink tea | 6:00 |
> ;;`--
>
> I would have expected something this:
>
> ;;,-
> ;;| Thursday4 December 2014 | 7:00 |
> ;;|8:00..
> ;;| * Nail org mode bug | 1:00 |
> ;;| * Drink tea | 6:00 |
> ;;`-
>
> and am therefore disappointed.
>
> I haven't investigated if this happens for simple clocked time as well
> as appointments yet.
>
> Myles
>
> P.S. Sorry for the ugly boxes, I can't remember how to get the nice
> ones.
>
>
Re: [O] [bug, patch, ox] INCLUDE and footnotes
Rasmus writes:
> Clearly the current situation is not satisfactory ("You can use :lines,
> but only if no footnotes are present. . . IOW, :lines supports a subset
> of Org syntax.").
>
> I prefer converting [fn:N] references to [fn::FOOTNOTE] (see my other
> email). Any obvious downsides?
Yes: inline and regular footnotes are not equivalent. For example,
a regular footnote can contain a table, a plain list... So this is not
an option here.
I think required definitions should be extracted from the included file
and inserted at the end of the source file, without any footnote
section. However, it would be nice to store associations between files
and footnote labels in, e.g., a hash table, in order to avoid inserting
multiple times the same footnote.
Regards,
Re: [O] table formula help...
Ok, done.
A clean design has been implemented for handling empty cells.
Basically, empty input cells are ignored, and therefore they do not
participate in the aggregation. (However, for aggregation using two
columns (=corr(p,q)= for example), if a pair of cells contains both an
empty and a non-empty cell, then the empty one is replaced by zero.)
On output, empty cells are generated when the aggregation function does
not have enough input. For instance, =mean= needs at least one value,
otherwise a division by zero happens.
Thanks to Michael Brand for his insight and suggestions.
Source code and documentation here:
https://github.com/tbanel/orgaggregate
Melpa installation:
(require 'package)
(add-to-list 'package-archives
'("melpa" . "http://melpa.milkbox.net/packages";)
t)
(package-initialize)
M-x package-list-packages
install orgtbl-aggregate
Have fun
Thierry
Re: [O] CLOCKSUM counts appointments excluded by tag
On 9 December 2014 at 21:35, Myles English wrote:
> I made a mistake in my first mail: the totals are for the Effort property
> not CLOCKSUM.
>
> Can no one confirm this? Is there something else wrong with my post? The
> situation is the same after pulling from master today.
>
>
> On 4 December 2014 at 22:58, Myles English wrote:
>
>> Hello,
>>
>> I am using git master from yesterday (commit 6d2a661f) and have found
>> that when the agenda is narrowed by tag (i.e. all appointments marked
>> with a certain tag are excluded), the clocksum still shows the
>> un-narrowed total. Is this the correct behaviour, or a bug?
>>
>> Selected variables:
>>
>> org-agenda-columns-add-appointments-to-effort-sum is t
>> org-columns-default-format:
>> "%80ITEM(Task) %10Effort(Effort){:} %10Duration(Duration){:} %10CLOCKSUM"
>>
>> org-global-properties:
>> (("Effort_ALL" . "0:00 0:10 0:30 1:00 2:00 3:00 4:00 5:00 6:00 7:00 8:00
>> 16:00 24:00 32:00"))
>>
>> Test org file:
>>
>>
>> ;;,--
>> ;;| * Nail org mode bug
>> ;;| SCHEDULED: <2014-12-04 Thu 9:00-10:00>
>> ;;|
>> ;;| * Earn money
>> :spouse:
>> ;;| SCHEDULED: <2014-12-04 Thu 09:00-20:00>
>> ;;|
>> ;;| * Drink tea
>> ;;| SCHEDULED: <2014-12-04 Thu 10:00-16:00>
>>
>> ;;`--
>>
>>
>> C-c a < a ;; get the agenda for the current test file
>> C-c C-x C-c ;; turn on column view
>>
>> ;;,--
>> ;;| Thursday4 December 2014 | 18:00 |
>> ;;|8:00..
>> ;;| * Nail org mode bug | 1:00 |
>> ;;| * Earn money| 11:00 |
>> ;;| * Drink tea | 6:00 |
>> ;;`--
>>
>>
>> / - TAB 'spouse' ;; narrow by excluding the item tagged 'spouse'
>>
>> See how the 18:00 has counted the 11:00 that should have been excluded:
>>
>> ;;,--
>> ;;| Thursday4 December 2014 | 18:00 |
>> ;;|8:00..
>> ;;| * Nail org mode bug | 1:00 |
>> ;;| * Drink tea | 6:00 |
>> ;;`--
>>
>> I would have expected something this:
>>
>> ;;,-
>> ;;| Thursday4 December 2014 | 7:00 |
>> ;;|8:00..
>> ;;| * Nail org mode bug | 1:00 |
>> ;;| * Drink tea | 6:00 |
>> ;;`-
>>
>> and am therefore disappointed.
>>
>> I haven't investigated if this happens for simple clocked time as well
>> as appointments yet.
>>
>
Yes, I can see similar behaviour for clocked tasks. That is to say, with
this file contents:
#+COLUMNS: %40ITEM(Task) %17Effort(Estimated Effort){:} %CLOCKSUM
* TODO Earn money
:PROPERTIES:
:Effort: 0:10
:END:
* TODO Drink tea :a:
:PROPERTIES:
:Effort: 0:30
:END:
#start emacs
$ emacs -Q
M-x org-agenda
< ;; narrow to current buffer
t ;; see all TODOs
C-c C-x C-c ;; see column view
/ - TAB a ;; exclude the item tagged :a:
And the result looks something like this:
Task | Estimated
Effort
Global list of TODO items of type: ALL
Available with `N r': (0)[ALL] (1)TODO | 0:40
TODO Earn money | 0:10
Myles
Re: [O] [bug, patch, ox] INCLUDE and footnotes
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Clearly the current situation is not satisfactory ("You can use :lines,
>> but only if no footnotes are present. . . IOW, :lines supports a subset
>> of Org syntax.").
>>
>> I prefer converting [fn:N] references to [fn::FOOTNOTE] (see my other
>> email). Any obvious downsides?
>
> Yes: inline and regular footnotes are not equivalent. For example,
> a regular footnote can contain a table, a plain list... So this is not
> an option here.
Damn. I only saw this after changing my path to this behavior. Good
point anyway. Though the idea of a table in a footnote is truly
horrifying.
> I think required definitions should be extracted from the included file
> and inserted at the end of the source file, without any footnote
> section.
The "hard" solution. I will look into it.
> However, it would be nice to store associations between files
> and footnote labels in, e.g., a hash table, in order to avoid inserting
> multiple times the same footnote.
What is your reasoning for this statement? Aesthetics, performance or
something else?
—Rasmus
--
Dobbelt-A
Re: [O] open file link in dired?
Alan Schmitt writes: > Hi Bastien, > > On 2013-01-04 17:33, Bastien writes: > >> Hi Alan, >> >> Alan Schmitt writes: >> >>> Thank you, this would work nicely. However I don't know how to specify, >>> when I open the file, which link-type to use. Would I need to modify the >>> link itself from "file" to "file+emacs+dired" before opening it? >> >> Trying loading the attached .el file to get a new "dired" type. >> Very crude but should work. > > I finally got around to test this, and here is a slightly improved > version that handles filenames with spaces. > > #+begin_src emacs-lisp > (org-add-link-type "file+emacs+dired" 'org-open-file-with-emacs-dired) > (add-hook 'org-store-link-functions 'org-dired-store-link) > > (defun org-open-file-with-emacs-dired (path) > "Open in dired." > (let ((d (file-name-directory path)) > (f (file-name-nondirectory path))) > (dired d) > (goto-char (point-min)) > (search-forward f nil t))) > > (defun org-dired-store-link () > "Store link to files/directories from dired." > (require 'dired+) > (when (eq major-mode 'dired-mode) > (let ((f (dired-get-filename))) > (setq link (concat "file+emacs+dired" ":" f) > desc (concat f " (dired)")) > (org-add-link-props :link link :description desc) > link))) > #+end_src > > Thanks again (and thanks to Org for letting me remember this 18 months > old task), > > Alan I've been searching many moons for this exact functionality! I'm very glad to run across this, but as a fairly new emacser, I'm not sure what to do with this code. I copied it into my init.el, marked it and ran 'eval-region', but what do I call to use the functions? If I can get this working, I will be using it every day. Thank you! steven arntson
Re: [O] open file link in dired?
(I replied to Steve directly but forgot to copy the list. Here it is.) On 2014-12-09 19:05, Steven Arntson writes: > I've been searching many moons for this exact functionality! I'm very > glad to run across this, but as a fairly new emacser, I'm not sure what > to do with this code. I copied it into my init.el, marked it and ran > 'eval-region', but what do I call to use the functions? If I can get this > working, I will be using it every day. - open a directory in dired mode - put the cursor on the file you want to link to - call `org-store-link' (which may be bound to `C-c l') The link is now stored. You can insert in an org file it with `org-insert-link' (often bound to `C-c C-l'). Alternatively, you can use an org-capture template that captures a link to the current context, and use it in dired mode. Best, Alan -- OpenPGP Key ID : 040D0A3B4ED2E5C7 signature.asc Description: PGP signature
