Re: [O] Beamer and org-language source blocks?
On Nov 1, 2013 4:35 PM, "Nicolas Goaziou" wrote: > Blocks cannot contain headlines. You need to protect offending lines > with a comma. See section 11.3 from the manual. I see it now... I was looking in the manual for info on source blocks, and didn't realize I needed to go up a conceptual level, to blocks-in-general. Thanks. hjh
Re: [O] org-store-link programmatically?
Josiah Schwab writes: > Hi David, > >> i want to write a piece of code as a 'template', which generates TODO >> using capture template, and inserts into the todo a LINK TO THE >> LOCATION, from which I have called the org-capture. > > Have you looked at "9.1.3 Capture templates" in the documentation? > http://orgmode.org/manual/Capture-templates.html > > It seems to me that the example TODO entry given (using "%a" in the > template) will do what you describe: > > , > | During expansion of the template, %a has been replaced by a link to > | the location from where you called the capture command. This can be > | extremely useful for deriving tasks from emails, for example. > ` > > Best, > Josiah Right! Thanks for hint. I did not see this one. Does exactly what I wanted to achieve nice weekend .d.
Re: [O] org-store-link programmatically?
Hi David, > i want to write a piece of code as a 'template', which generates TODO > using capture template, and inserts into the todo a LINK TO THE > LOCATION, from which I have called the org-capture. Have you looked at "9.1.3 Capture templates" in the documentation? http://orgmode.org/manual/Capture-templates.html It seems to me that the example TODO entry given (using "%a" in the template) will do what you describe: , | During expansion of the template, %a has been replaced by a link to | the location from where you called the capture command. This can be | extremely useful for deriving tasks from emails, for example. ` Best, Josiah
[O] org-store-link programmatically?
Dear all,
i want to write a piece of code as a 'template', which generates TODO
using capture template, and inserts into the todo a LINK TO THE
LOCATION, from which I have called the org-capture.
the main usage for me is basically when I get email message (notmuch),
to generate a journal entry with some comments and at the end of this
entry a link to that email.
I thought like defining a function like this one:
(defun org-notmuch-copymail ()
(interactive)
(org-store-link)
;; some code to get the link into the yank buffer
(org-capture nil "c"))
where the 'c' template is defined as follows:
("c" "Global todo entry with clipboard content" entry (file+headline (concat
my-org-files "gtd.org") "Tasks")
"* TODO %?\n:LOGBOOK:\n%c\n:END:\n")
The trouble #1 I have is a call to (org-store-link), which always fails,
because it requires 'an argument' I have a hard time to find which one.
One of the options I was considering was as well to 'construct' the link
myself. That requires some 'generalization' as I would have to detect
(somehow) what type of buffer it is. As filelinks:
[[mylink.png][sometext]]
are different from notmuch links:
[[notmuch:id:75a7a46b727b42dca8c70b1c64db0...@cernfe23.cern.ch][email]]
Any ideas how to solve this?
As a bonus question: I've noticed, that when I store link, and then
paste it, it pastes the files using absolute paths. I would very much
prefer relative paths. Is there any way how to change this behaviour?
many thanks
david
Re: [O] Bug: = symbol in url converted to %3D [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/local/share/emacs/24.3.50/lisp/org/)]
Sorry, i screwed up my cut and paste there. In test.org, the link has an =
sign, not %3D.
Tyler
Sent with AquaMail for Android
http://www.aqua-mail.com
On November 1, 2013 5:10:38 PM Tyler Smith wrote:
MWE:
test.org
* This is a test.
A link [[http://seqanswers.com/forums/showthread.php?t%3D21][to
seqanswers.com]].
Exporting to latex from org-mode produces the following file:
test.tex
% Created 2013-11-01 Fri 16:37
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\providecommand{\alert}[1]{\textbf{#1}}
\title{test}
\author{Tyler Smith}
\date{\today}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs Org-mode version 7.9.3f}}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
\section{This is a test.}
\label{sec-1}
Here's a line of text with a link
\href{http://seqanswers.com/forums/showthread.php?t%3D21}{to
seqanswers.com}.
\end{document}
Note that the url has been converted from:
http://seqanswers.com/forums/showthread.php?t=21
to:
http://seqanswers.com/forums/showthread.php?t%3D21
This effectively breaks the link. This is not specific to the latex
exporter, it happens also in at least the markdown exporter.
Note also that I have reproduced the problem in a newer version of org:
[8.2.1 (8.2.1-21-g2b3e01-elpa @ /home/tws/.emacs.d/elpa/org-20131028/)]
Thanks,
Tyler
Emacs : GNU Emacs 24.3.50.1 (i686-pc-linux-gnu, GTK+ Version 3.8.2)
of 2013-08-20 on ONOTTAR654746
Package: Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @
/usr/local/share/emacs/24.3.50/lisp/org/)
current state:
==
(setq
org-export-blocks '((src org-babel-exp-src-block nil)
(export-comment org-export-blocks-format-comment t)
(ditaa org-export-blocks-format-ditaa nil)
(dot org-export-blocks-format-dot nil))
org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
org-export-preprocess-before-selecting-backend-code-hook
'(org-beamer-select-beamer-code)
org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
org-babel-hide-result-toggle-maybe org-babel-header-arg-expand)
org-cycle-hook '(org-cycle-hide-archived-subtrees
org-cycle-hide-drawers org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-babel-pre-tangle-hook '(save-buffer)
org-occur-hook '(org-first-headline-recenter)
org-export-interblocks '((src org-babel-exp-non-block-elements))
org-metaup-hook '(org-babel-load-in-session-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
org-export-latex-format-toc-function 'org-export-latex-format-toc-default
org-export-preprocess-before-normalizing-links-hook
'(org-remove-file-link-modifiers)
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-export-first-hook '(org-beamer-initialize-open-trackers)
org-mode-hook '(#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook org-show-block-all
append local] 5]
#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook
org-babel-show-result-all append local] 5]
org-babel-result-hide-spec org-babel-hide-all-hashes)
org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc
org-beamer-auto-fragile-frames
org-beamer-place-default-actions-for-lists)
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-confirm-shell-link-function 'yes-or-no-p
)
[O] Bug: = symbol in url converted to %3D [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/local/share/emacs/24.3.50/lisp/org/)]
MWE:
test.org
* This is a test.
A link [[http://seqanswers.com/forums/showthread.php?t%3D21][to
seqanswers.com]].
Exporting to latex from org-mode produces the following file:
test.tex
% Created 2013-11-01 Fri 16:37
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\providecommand{\alert}[1]{\textbf{#1}}
\title{test}
\author{Tyler Smith}
\date{\today}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs Org-mode version 7.9.3f}}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
\section{This is a test.}
\label{sec-1}
Here's a line of text with a link
\href{http://seqanswers.com/forums/showthread.php?t%3D21}{to
seqanswers.com}.
\end{document}
Note that the url has been converted from:
http://seqanswers.com/forums/showthread.php?t=21
to:
http://seqanswers.com/forums/showthread.php?t%3D21
This effectively breaks the link. This is not specific to the latex
exporter, it happens also in at least the markdown exporter.
Note also that I have reproduced the problem in a newer version of org:
[8.2.1 (8.2.1-21-g2b3e01-elpa @ /home/tws/.emacs.d/elpa/org-20131028/)]
Thanks,
Tyler
Emacs : GNU Emacs 24.3.50.1 (i686-pc-linux-gnu, GTK+ Version 3.8.2)
of 2013-08-20 on ONOTTAR654746
Package: Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @
/usr/local/share/emacs/24.3.50/lisp/org/)
current state:
==
(setq
org-export-blocks '((src org-babel-exp-src-block nil)
(export-comment org-export-blocks-format-comment t)
(ditaa org-export-blocks-format-ditaa nil)
(dot org-export-blocks-format-dot nil))
org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
org-export-preprocess-before-selecting-backend-code-hook
'(org-beamer-select-beamer-code)
org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
org-babel-hide-result-toggle-maybe org-babel-header-arg-expand)
org-cycle-hook '(org-cycle-hide-archived-subtrees
org-cycle-hide-drawers org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-babel-pre-tangle-hook '(save-buffer)
org-occur-hook '(org-first-headline-recenter)
org-export-interblocks '((src org-babel-exp-non-block-elements))
org-metaup-hook '(org-babel-load-in-session-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
org-export-latex-format-toc-function 'org-export-latex-format-toc-default
org-export-preprocess-before-normalizing-links-hook
'(org-remove-file-link-modifiers)
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-export-first-hook '(org-beamer-initialize-open-trackers)
org-mode-hook '(#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook org-show-block-all
append local] 5]
#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook
org-babel-show-result-all append local] 5]
org-babel-result-hide-spec org-babel-hide-all-hashes)
org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc
org-beamer-auto-fragile-frames
org-beamer-place-default-actions-for-lists)
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-confirm-shell-link-function 'yes-or-no-p
)
[O] (idea?) fontification of live code blocks
Hello. I don't know if this has been mentioned before, but it would be nice
to have fontified live code blocks, since sometimes it's hard to clearly
distinguish---at least at first sight---between regular text and something
like, for example, src_R[:session
*project2*]{round(mean(data$AGE),digits=0)}.
Re: [O] Setting properties when scrolling around buffer puts property in wrong headline
John Hendy writes: >> I'm supposing there's no way around this... but I'm creating a >> taskjuggler document that's fairly wrong. I often find myself in a >> situation where I go to set a :depends: property to reference another >> headline and need to go see what it's task_id is. So, I scroll down, >> look at the task, then enter the correct task_id in the minibuffer >> (which is still active after doing C-c C-x p property-name RET), and >> then find that it's been inserted in a different headline since >> scrolling moves the point/cursor to a different headline. I would say its the expected behaviour - when the mini-buffer is still active, the command wasn't sent yet, and when you finally send it, Org-mode acts on the property drawer where point is at that moment. You might want to read about using the mark, i.e. how to set the mark before searching the task-id, and then go back to that point before sending the command from the mini-buffer: ,-- | http://www.gnu.org/software/emacs/manual/html_node/emacs/Mark-Ring.html#Mark-Ring `-- -- cheers, Thorsten
Re: [O] Arbitrary lisp functions in column-attributes
Hi Aaron, I hadn't actually foreseen using it for column-view so much, but rather for a dynamic-block which generates a column-view of a tree. These are, as far as I understand, read-only. I don't think it would work well with read-write column-views, so if such a function were defined in the :COLUMNS: property, it should either be ignored and not displayed in the R/W column-view, or it could be displayed if there were some way of ensuring that the associated column was R/O. Maybe others have a better idea on how to handle this? I am somewhat partial to the scheme used in org-collector, where columns are defined at the beginning of a dynamic block, and not in the original tree. This way you can have several different dynamic blocks which summarize the tree-data in different ways. It would also allow the column-definitions defined in the tree to be used only for the R/W column-view of that tree. Regards, Mark On Thu, Oct 31, 2013 at 1:56 PM, Aaron Ecay wrote: > Hi Mark, > > This seems like an intriguing idea. I have just one question: how would > this interact with editing in column view? Would function-valued > property columns be read only? Or do you have something different in > mind? > > -- > Aaron Ecay
Re: [O] Setting properties when scrolling around buffer puts property in wrong headline
Bump... at the least, wondering if this is intended/expected, or if it's a genuine issue. Perhaps no one else encounters this? John On Sat, Oct 26, 2013 at 11:11 PM, John Hendy wrote: > Greetings, > > > I'm supposing there's no way around this... but I'm creating a > taskjuggler document that's fairly wrong. I often find myself in a > situation where I go to set a :depends: property to reference another > headline and need to go see what it's task_id is. So, I scroll down, > look at the task, then enter the correct task_id in the minibuffer > (which is still active after doing C-c C-x p property-name RET), and > then find that it's been inserted in a different headline since > scrolling moves the point/cursor to a different headline. > > Again, I'm thinking that Emacs just works differently than other > programs in that the cursor appears to move to stay in the view of the > current buffer vs. staying at the existing point regardless of where > I'm looking in the file. > > Is there a way around this issue? Almost like remembering the MARK > where either 1) the command was initiated or 2) where it was when the > property name was typed, followed by RET (but prior to setting the > value) vs. wherever the cursor ends up between setting the property > name and actually setting the value? > > > Thanks! > John > > P.S. if the issue is unclear, open up a longer Org document and unfold > enough headlines so that the entire file cannot be viewed within the > height. Go a headline near the top and do C-c C-x p. Type a property > name and press RET. Now scroll down a bit in the buffer and then type > in the name of the property and press RET. The property will be > inserted in whatever headline you're cursor scrolled down to, not the > headline in which you initiated the command.
Re: [O] fold all drawers in a buffer?
Aaron Ecay writes: Hi Aaron, > 2013ko azaroak 1an, Thorsten Jolitz-ek idatzi zuen: >> I tested the above functions with a big org file - way to slow. >> These versions perfom better, but only on property drawers: >> >> #+begin_src emacs-lisp >> (defun org-show-drawers () >> "Unfold all drawers in buffer" >> (interactive) >> (save-excursion >> (goto-char (point-min)) >> (while (re-search-forward org-property-start-re nil 'NOERROR) >> (and (org-element-property :hiddenp (org-element-at-point)) >> (org-cycle) >> >> (defun org-hide-drawers () >> "Unfold all drawers in buffer" >> (interactive) >> (save-excursion >> (goto-char (point-min)) >> (while (re-search-forward org-property-start-re nil 'NOERROR) >> (and (not (org-element-property :hiddenp >> (org-element-at-point))) >> (org-cycle) >> #+end_src > > This will work on recent versions of org, but the :hiddenp properties > were taken out of the parser by the following git commit (not yet in any > released version of org AFAIK): > > commit fe27ca9906f1d6c48a93f463d85850925687b825 > Author: Nicolas Goaziou > Date: Thu Oct 3 22:57:02 2013 +0200 > > For forward compatibility you can skip the visibility check and use > ‘(org-flag-drawer nil)’ unconditionally, I think. I see, thanks for the tip. I did not know about the fate of 'hiddenp' or about the useful 'org-flag-XXX' functions. -- cheers, Thorsten
Re: [O] fold all drawers in a buffer?
Hi Thorsten, 2013ko azaroak 1an, Thorsten Jolitz-ek idatzi zuen: > I tested the above functions with a big org file - way to slow. > These versions perfom better, but only on property drawers: > > #+begin_src emacs-lisp > (defun org-show-drawers () > "Unfold all drawers in buffer" > (interactive) > (save-excursion > (goto-char (point-min)) > (while (re-search-forward org-property-start-re nil 'NOERROR) > (and (org-element-property :hiddenp (org-element-at-point)) > (org-cycle) > > (defun org-hide-drawers () > "Unfold all drawers in buffer" > (interactive) > (save-excursion > (goto-char (point-min)) > (while (re-search-forward org-property-start-re nil 'NOERROR) > (and (not (org-element-property :hiddenp (org-element-at-point))) > (org-cycle) > #+end_src This will work on recent versions of org, but the :hiddenp properties were taken out of the parser by the following git commit (not yet in any released version of org AFAIK): commit fe27ca9906f1d6c48a93f463d85850925687b825 Author: Nicolas Goaziou Date: Thu Oct 3 22:57:02 2013 +0200 For forward compatibility you can skip the visibility check and use ‘(org-flag-drawer nil)’ unconditionally, I think. -- Aaron Ecay
Re: [O] org-writers-room sort of works! just in time for NaNoWriMo
Matt Price writes: > On Fri, Nov 1, 2013 at 2:08 AM, Alan L Tyree wrote: >> >> Matt Price writes: >> >>> I have just pushed a more-or-less-working version of my "Org Writer's >>> Room" mode to github: >>> >> >>> PS, the readme on github is a little out of date, but the code itself >>> is mostly documented so I hope that helps. Though there's no general >>> documentation at the top of the file -- oops, sorry. >> >> Hi Matt, >> Looks very promising. My first look at it and the middle "column" >> doesn't preserve visual line mode. I have taken to using this a lot >> since it is much easier to interact with non-emacs/org-mode users. > > Do you load visual line mode automatically when you load org-mode? if > not it will definitely be broken, as I have to manually set the major > and minor modes on the new buffers (if I don't do that, all indirect > buffers will have the same modes as the parent buffer, which I don't > want). I bet there's a way to record all the minor modes in a buffer, > then reload them in the indirect buffer, but I don't know it. Does > anyone else out there? Yes, I have the following line at the top of the file: # -*- mode: visual-line; mode: org; fill-column: 1000; -*- >> >> I'll put it through some more testing in the next day or so. >> >> Also would like your ideas on useful properties. I have 'edition' and >> 'status' (review, in-progress, draft, submitted, final). I know you are >> aiming at fiction, but I'm sure your ideas would be welcome. > > I'm only sort of aiming at fiction as I don't really write fiction, so > I think "status" is great. I'm not so sure about "edition" -- when > would you use that, do you think? You may have noticed in any case > that org-writers-room-properties is a defcustom, so it an be tweaked > by hand if you think your use case is uncommon. The document is a law textbook that is now going into its 8th edition. I keep it under version control but it is handy to know at a glance which sections I have updated, etc. Cheers, Alan > > I'm sure you will find lots more bugs -- the mode isn't very > well-constructed, and in particular it doesn't dismantle itself very > well -- really it should remember the existing window arrangement and > restore it when it quits... > > Please feel free to hack away at it! > >> >> Cheers, >> Alan >> >> >> -- >> Alan L Tyree http://www2.austlii.edu.au/~alan >> Tel: 04 2748 6206 sip:172...@iptel.org -- Alan L Tyree http://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:172...@iptel.org
Re: [O] Babel Tangle issues
Sam Flint writes: > I use org-babel to LP, and when I go to tangle, I get very little > output, a shebang line and that is about it, I have noweb set to tangle, > yet my references do not resolve. Any ideas why? Without a minimal example illustrating the problem it is impossible to say. The following tiny example works as expected. This, #+Title: example of tangling with noweb * Two noweb blocks #+name: begin #+begin_src sh echo begin #+end_src #+name: end #+begin_src sh echo end #+end_src * Containing tangled block #+begin_src sh :tangle yes :noweb tangle <> date <> #+end_src tangles to this, echo begin date echo end Best, -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
[O] Babel Tangle issues
I use org-babel to LP, and when I go to tangle, I get very little output, a shebang line and that is about it, I have noweb set to tangle, yet my references do not resolve. Any ideas why? -- Sam Flint swfl...@flintfam.org freenode: swflint (402) 517-8468 http://flintfam.org/~swflint BAFBF3FF
[O] ATTN: Bernt Hansen, regarding org-mode.org
Hello, Bernt. According to your famous org-mode.org document (thank you!) this file: http://doc.norang.ca/org-mode.org.html ...should be a colorized version of the org source. Please take a look at it. The total filesize seems lower than I'd expect. ;) Thanks, cheers, --Dave
Re: [O] fold all drawers in a buffer?
Thorsten Jolitz writes: > Matt Price writes: > >> Is there a command to fold all drawers in a buffer (all property >> drawers would be enough, actually)? Or a suggestion for how to do >> this? Thanks! > > They might exist (with me unaware of them), but the following pair of > commands does the job, at least with this minimal test org snippet: > > * A > :PROPERTIES: > :CUSTOM_ID: a1 > :END: > * B > :PROPERTIES: > :CUSTOM_ID: B1 > :END: > > #+begin_src emacs-lisp > (defun org-show-drawers () > "Unfold all drawers in buffer" > (interactive) > (save-excursion > (goto-char (point-min)) > (while (not (eobp)) > (and (org-at-drawer-p) > (org-element-property :hiddenp (org-element-at-point)) > (org-cycle)) > (forward-char > > (defun org-hide-drawers () > "Fold all drawers in buffer" > (interactive) > (save-excursion > (goto-char (point-min)) > (while (not (eobp)) > (and (org-at-drawer-p) > (not (org-element-property :hiddenp (org-element-at-point))) > (org-cycle)) > (forward-char > #+end_src > > #+results: > : org-hide-drawers I tested the above functions with a big org file - way to slow. These versions perfom better, but only on property drawers: #+begin_src emacs-lisp (defun org-show-drawers () "Unfold all drawers in buffer" (interactive) (save-excursion (goto-char (point-min)) (while (re-search-forward org-property-start-re nil 'NOERROR) (and (org-element-property :hiddenp (org-element-at-point)) (org-cycle) (defun org-hide-drawers () "Unfold all drawers in buffer" (interactive) (save-excursion (goto-char (point-min)) (while (re-search-forward org-property-start-re nil 'NOERROR) (and (not (org-element-property :hiddenp (org-element-at-point))) (org-cycle) #+end_src -- cheers, Thorsten
Re: [O] fold all drawers in a buffer?
Matt Price writes: > Is there a command to fold all drawers in a buffer (all property > drawers would be enough, actually)? Or a suggestion for how to do > this? Thanks! They might exist (with me unaware of them), but the following pair of commands does the job, at least with this minimal test org snippet: * A :PROPERTIES: :CUSTOM_ID: a1 :END: * B :PROPERTIES: :CUSTOM_ID: B1 :END: #+begin_src emacs-lisp (defun org-show-drawers () "Unfold all drawers in buffer" (interactive) (save-excursion (goto-char (point-min)) (while (not (eobp)) (and (org-at-drawer-p) (org-element-property :hiddenp (org-element-at-point)) (org-cycle)) (forward-char (defun org-hide-drawers () "Fold all drawers in buffer" (interactive) (save-excursion (goto-char (point-min)) (while (not (eobp)) (and (org-at-drawer-p) (not (org-element-property :hiddenp (org-element-at-point))) (org-cycle)) (forward-char #+end_src #+results: : org-hide-drawers -- cheers, Thorsten
Re: [O] org-writers-room sort of works! just in time for NaNoWriMo
Matt Price writes: Hi, > Do you load visual line mode automatically when you load org-mode? if > not it will definitely be broken, as I have to manually set the major > and minor modes on the new buffers (if I don't do that, all indirect > buffers will have the same modes as the parent buffer, which I don't > want). I bet there's a way to record all the minor modes in a buffer, > then reload them in the indirect buffer, but I don't know it. Does > anyone else out there? I have this (stolen) function in outorg.el: ,--- | ;; courtesy to Trey Jackson (http://tinyurl.com/cbnlemg) | (defun outorg-which-active-modes () | "Give a message of which minor modes are enabled in the current buffer." | (interactive) | (let ((active-modes)) | (mapc | (lambda (mode) |(condition-case nil |(if (and (symbolp mode) (symbol-value mode)) |(add-to-list 'active-modes mode)) | (error nil) )) | minor-mode-list) | ;; (message "Active modes are %s" active-modes) | active-modes)) `--- -- cheers, Thorsten
Re: [O] org-writers-room sort of works! just in time for NaNoWriMo
On Fri, Nov 1, 2013 at 5:07 AM, Ian Barton wrote: > On 01/11/13 06:08, Alan L Tyree wrote: >> >> >> Matt Price writes: >> >>> I have just pushed a more-or-less-working version of my "Org Writer's >>> Room" mode to github: >>> >> >>> >>> PS, the readme on github is a little out of date, but the code itself >>> is mostly documented so I hope that helps. Though there's no general >>> documentation at the top of the file -- oops, sorry. >> >> >> Hi Matt, >> Looks very promising. My first look at it and the middle "column" >> doesn't preserve visual line mode. I have taken to using this a lot >> since it is much easier to interact with non-emacs/org-mode users. >> >> I'll put it through some more testing in the next day or so. >> > > Thanks for sharing it. I have just started on a short non-fiction book and I > can see it being very useful. If only you could add a "Locked cell with no > Internet connection, or other distractions" mode. I could use that mode too. Maybe someone on the list can implement it? > > Ian. > >
Re: [O] org-writers-room sort of works! just in time for NaNoWriMo
On Fri, Nov 1, 2013 at 2:08 AM, Alan L Tyree wrote: > > Matt Price writes: > >> I have just pushed a more-or-less-working version of my "Org Writer's >> Room" mode to github: >> > >> PS, the readme on github is a little out of date, but the code itself >> is mostly documented so I hope that helps. Though there's no general >> documentation at the top of the file -- oops, sorry. > > Hi Matt, > Looks very promising. My first look at it and the middle "column" > doesn't preserve visual line mode. I have taken to using this a lot > since it is much easier to interact with non-emacs/org-mode users. Do you load visual line mode automatically when you load org-mode? if not it will definitely be broken, as I have to manually set the major and minor modes on the new buffers (if I don't do that, all indirect buffers will have the same modes as the parent buffer, which I don't want). I bet there's a way to record all the minor modes in a buffer, then reload them in the indirect buffer, but I don't know it. Does anyone else out there? > > I'll put it through some more testing in the next day or so. > > Also would like your ideas on useful properties. I have 'edition' and > 'status' (review, in-progress, draft, submitted, final). I know you are > aiming at fiction, but I'm sure your ideas would be welcome. I'm only sort of aiming at fiction as I don't really write fiction, so I think "status" is great. I'm not so sure about "edition" -- when would you use that, do you think? You may have noticed in any case that org-writers-room-properties is a defcustom, so it an be tweaked by hand if you think your use case is uncommon. I'm sure you will find lots more bugs -- the mode isn't very well-constructed, and in particular it doesn't dismantle itself very well -- really it should remember the existing window arrangement and restore it when it quits... Please feel free to hack away at it! > > Cheers, > Alan > > > -- > Alan L Tyree http://www2.austlii.edu.au/~alan > Tel: 04 2748 6206 sip:172...@iptel.org
[O] fold all drawers in a buffer?
Is there a command to fold all drawers in a buffer (all property drawers would be enough, actually)? Or a suggestion for how to do this? Thanks! Matt
Re: [O] org-writers-room sort of works! just in time for NaNoWriMo
On 01/11/13 06:08, Alan L Tyree wrote: Matt Price writes: I have just pushed a more-or-less-working version of my "Org Writer's Room" mode to github: PS, the readme on github is a little out of date, but the code itself is mostly documented so I hope that helps. Though there's no general documentation at the top of the file -- oops, sorry. Hi Matt, Looks very promising. My first look at it and the middle "column" doesn't preserve visual line mode. I have taken to using this a lot since it is much easier to interact with non-emacs/org-mode users. I'll put it through some more testing in the next day or so. Thanks for sharing it. I have just started on a short non-fiction book and I can see it being very useful. If only you could add a "Locked cell with no Internet connection, or other distractions" mode. Ian.
Re: [O] Beamer and org-language source blocks?
Hello, James Harkins writes: > ** What I mean and what I see > #+begin_src org :exports code > ** Overview > *** This talk will cover: > - bla bla > #+end_src > > --> And in the output, you can see that it takes "** Overview" as a new > frame and treats the #+begin/end_src markers as regular text. Huh? Blocks cannot contain headlines. You need to protect offending lines with a comma. See section 11.3 from the manual. Regards, -- Nicolas Goaziou
