Re: [O] [proposal] timezone-aware timestamps enhancement
Hi Eric, I've also seen these threads from the archive of the mailing list discussing about the very same thing. In summary it seems that in 2008 Carsten's opinion on this was that it would add a lot of complexity and it's a pandora's box about to be open. In 2014, Nicolas's reply seems a bit more encouraging. http://thread.gmane.org/gmane.emacs.orgmode/93082/focus=93082 http://thread.gmane.org/gmane.emacs.orgmode/5145/focus=5145 On Wed, Mar 18, 2015 at 04:33:44PM +, Eric S Fraga wrote: There is no specific solution unfortunately. Having spent a year living and working across time zones, I was unable to find a good solution. And, in fact, the problem was compounded by trying to synchronise org data with Google's calendar and with MS Outlook. I eventually simply stopped synchronising and relied on my computer having the time that was appropriate for where I was at the time. All So would your computer find out the timezone and switch it automatically ? (IIRC Ubuntu does that by default) On Wed, Mar 18, 2015 at 04:33:44PM +, Eric S Fraga wrote: org data were local time with a fluid definition of local. I'd be interested in knowing a bit more about the fluid definition.
Re: [O] [proposal] timezone-aware timestamps enhancement
On Wed, Mar 18, 2015 at 02:09:31PM -0400, Ken Mankoff wrote: I have a solution that works quite well outside of Org. Apple Calendar supports timezones plus a floating option. I use Org for all my floating events - local to the computer and me, whatever TZ we're in. I haven't found a way to put TZ-specific events into Org. If scheduling a Skype with someone in NZ, I enter it in iCal at the NZ time in the NZ timezone. Org pulls in my iCal events. Then wherever I am when that event happens, I get the alert at the correct time. Most things are local to me, so I use floating and stay in Org. I wrote a silly elisp function that does the conversion for me. Hah, yeah ! exactly, I use it for the exact same thing, scheduling an interview with someone on the other side of the planet. So for example they ask me Can you provide us with times when you're available for an interview ? and I just make a table and let them decide when: | time Tokyo | time Sofia | |+| | 2015-03-20 18:00 | 2015-03-20 Fri 11:00 | | 2015-03-21 14:00 | 2015-03-21 Sat 07:00 | | 2015-03-22 14:00 | 2015-03-22 Sun 07:00 | | 2015-03-23 14:00 | 2015-03-23 Mon 07:00 | | 2015-03-24 14:00 | 2015-03-24 Tue 07:00 | #+TBLFM: $1='(concat (org-tz-conv $2 Asia/Tokyo to) ) You said above you're using iCal (do you mean, Google Calendar or Apple Calendar?). I'd be interested in setting this up as well, which one should I be using ? At this point in time I'm using Org-Mode's agenda to view events. Should I try to sync them up with my phone and if so what is the recommended way to go ? This is the implementation of org-tz-conv: (defun org-tz-conv (stamp tz way) (let* ( (current-tz-offset (shell-command-to-string date +%z)) (stamp1(concat (replace-regexp-in-string [] stamp) current-tz-offset)) (date-cmd-p0 TZ=%s date -d \%s\) (date-cmd-p1 date --date=\TZ=\\\%s\\\ %s\) (date-cmd-p2 +\%F %H:%M\) (date-cmd-rendered1 (format date-cmd-p1 tz stamp1 )) (date-cmd-from (concat date-cmd-rendered1 date-cmd-p2)) (date-cmd-to(concat (format date-cmd-p0 tz stamp1) date-cmd-p2)) (shell-result-from (shell-command-to-string date-cmd-from )) (shell-result-to (shell-command-to-string date-cmd-to )) (result-from (replace-regexp-in-string \n shell-result-from) ) (result-to (replace-regexp-in-string \n shell-result-to ) ) ) (message shell-result-from) (message shell-result-to) (cond ((string-equal way from) result-from) ((string-equal way to ) result-to )) ))
[O] ID property generated by org-mobile
Does the ID property have any use? I know I can disable it, but where is it being used ? (the ID property that org-mobile generates for each heading) Are there any drawbacks to just disabling it with (setq org-mobile-force-id-on-agenda-items nil) ? Is it being used somewhere in particular ?
Re: [O] Config best practices?
Hello Marcin, Marcin Borkowski wrote: I'm wondering what people do to keep the configuration of their Org files in order. I'm not sure to correctly grasp your objective. Could you restate it? I use a dedicated top-level headline, with a COMMENT keyword, but I started to think that a :noexport: tag might be a better idea. Are there any advantages of one over the other, or other approaches altogether? I can tell you they aren't isomorphic... The noexport tag simply says don't export this subtree. The COMMENT keyword adds don't run any Babel code block in there. The reason I'm asking is that I'm tweaking my org-one-to-many utility so that it propagates the config to all the generated files. Still not that clear to me. Maybe an ECM would clarify your request? Best regards, Seb -- Sebastien Vauban
Re: [O] How to represent Emacs keystrokes in Org?
Hi Marcin,
I'm going to reference a hangout of Sacha Chua and Xah Lee
where they talked about this https://www.youtube.com/watch?v=rKPKWqvTImA
( you can download it with livestreamer like so
livestreamer -o xlsc.mp4 https://www.youtube.com/watch?v=rKPKWqvTImA 360p )
At 26:53 Xah Lee starts explaining about how his
setup related to rendering keystrokes in emacs.
At 27:13 he mentions this function = xhm-htmlize-keyboard-shortcut-notation
Apparently this is used to render the keystrokes.
On Thu, Mar 19, 2015 at 10:48:30PM +0100, Marcin Borkowski wrote:
Hi there,
it seems that reviving old threads is my new hobby;-).
On 2014-11-29, at 22:58, Marcin Borkowski mb...@wmi.amu.edu.pl wrote:
On 2014-11-29, at 22:53, Marcin Borkowski wrote:
On 2014-11-24, at 19:38, Rasmus wrote:
Marcin Borkowski mb...@wmi.amu.edu.pl writes:
Hello,
I'm writing (in Org) a text on Emacs usage. How to
correctly/canonically represent keystrokes, like C-x RET f?
Currently, I use =C-x RET f=; are there any alternatives?
That's what I'd do. Or ~C-x RET f~. You could also use a macro, if you
want it to me be more semantic (I hope I use this word correctly).
This might seem a good idea, but how do I do it? (See below for
a concrete problem statement.)
Houston, we've got a problem. What about =M-,=? Somehow it seems not
to be interpreted in the right way: it does not get fontified correctly,
nor does export in the right way. What can I do about it? I found
about org-emphasis-regexp-components, is it the only way? Also, how do
I reload Org without restarting Emacs? (I am an Emacs geek and I try to
beat my record of emacs-uptime, you know. ;-) )
Wow, I got an idea, and it worked. Here's an excerpt from `C-u C-x ='
at my solution;-):
position: 11859 of 16051 (74%), column: 253
character: (displayed as ) (codepoint 8205, #o20015, #x200d)
preferred charset: unicode (Unicode (ISO10646))
code point in charset: 0x200D
syntax: .which means: punctuation
to input: type C-x 8 RET HEX-CODEPOINT or C-x 8 RET NAME
buffer code: #xE2 #x80 #x8D
file code: #xE2 #x80 #x8D (encoded by coding system utf-8-unix)
display: by this font (glyph code)
xft:-unknown-Phetsarath
OT-normal-normal-normal-*-17-*-*-*-*-0-iso10646-1 (#x120)
Character code properties: customize what to show
name: ZERO WIDTH JOINER
A bit ugly trick, but works. What are the opinions?
After a while I have to say that my opinion is strongly negative: this
breaks LaTeX export. (LaTeX doesn’t like some unicode characters, it
turns out.) Also, this was really an ugly hack...
So, here is my problem: how to represent a key like M-, or
e.g. a sequence \, (important in regexps) as “code” or “verbatim stuff”
in org-mode? Neither =\,= nor ~\,~ work, of course. Also, I’d like
this to be backend-agnostic, so \texttt{M-,} doesn’t really work.
What is the rationale behind forbidding the comma as the “border”
character in org-emphasis-regexp-components? Should I change this
variable in my setup or is there a more general way to convince Org that
I really want verbatim/code snippets like =\,=?
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
[O] [org-element, FR] make secondary-string midnight compatible
Hi, As is evident from the git log, I have made the following mistake at least twice: (org-element-parse-secondary-string nil restrictions) I wish this would just return nil instead of an error. In particular, in ox files you have to do (org-element-parse-secondary-string (or whatever ) restrictions) Which is a bit noisy. For me the confusion arise because (org-export-data nil info) does not throw an error. Note, I have no idea if the error behavior is needed elsewhere, so it don't know how feasible this request is or if it's heretic for that matter. —Rasmus -- The right to be left alone is a human right
[O] [bug?, ox-latex] creator not commented out
Hi, In ox-latex :creator is inserted according to ;; Creator. (and (plist-get info :with-creator) (concat (plist-get info :creator) \n)) Is it on purpose that if :with-creator is non-nil and :creator is the default value, then it's inserted in the pdf, i.e. without being prefixed with %? —Rasmus -- One thing that is clear: it's all down hill from here
[O] [ox, patch] Add #+SUBTITLE
Hi,
This patch adds #+SUBTITLE to a couple of backends. This property is
already supported in ox-texinfo and e.g. beamer.cls has a subtitles macro,
but ox-beamer.el has no #+SUBTITLE. I have used subtitles in
e.g. applications for research funds.
The value-added is twofold:
- It adds a consistent way to have subtitle across backends. I'm
explicitly assuming this is nice, but perhaps this is false.
- Currently, it is, I believe, impossible to hack-up a subtitle in at
least ox-odt.el.
It's not documented yet as I want make sure that it's not an undesirable
feature before progressing further.
WDTY?
—Rasmus
--
The right to be left alone is a human right
From 4b9ce6f4d260360847bf63f3bab9f98004bc7469 Mon Sep 17 00:00:00 2001
From: Rasmus ras...@gmx.us
Date: Sun, 1 Mar 2015 22:09:19 +0100
Subject: [PATCH] ox: Add SUBTITLE property in some backends
* ox-ascii.el (org-ascii-template--document-title)
(org-ascii-template--document-title)
ox-deck.el (org-deck-title-slide-template)
ox-s5.el (org-s5-title-slide-template)
ox-html.el (org-html--build-meta-info, org-html-format-spec)
(org-html--build-meta-info, org-html-format-spec)
(org-html--build-meta-info, org-html-format-spec)
ox-org.el (org), (org-org-keyword): Use SUBTITLE.
* ox-beamer.el (org-beamer-template)
ox-html (org-html-template)
ox-latex.el (org-latex-template)
ox-org (org-org-template): Insert SUBTITLE.
* ox-html (org-html-preamble-format) (org-html-postamble-format):
Update docstring.
* ox-html (org-html-style-default): Add style for SUBTITLE.
---
contrib/lisp/ox-deck.el | 2 ++
contrib/lisp/ox-s5.el | 2 ++
lisp/ox-ascii.el| 23 ++-
lisp/ox-beamer.el | 10 +-
lisp/ox-html.el | 26 --
lisp/ox-latex.el| 35 +--
lisp/ox-odt.el | 32 +---
lisp/ox-org.el | 9 +++--
8 files changed, 120 insertions(+), 19 deletions(-)
diff --git a/contrib/lisp/ox-deck.el b/contrib/lisp/ox-deck.el
index 0ebde41..a76384b 100644
--- a/contrib/lisp/ox-deck.el
+++ b/contrib/lisp/ox-deck.el
@@ -259,6 +259,7 @@ Defaults to styles for the title page.
(defcustom org-deck-title-slide-template
h1%t/h1
+h2%s/h2
h2%a/h2
h2%e/h2
h2%d/h2
@@ -446,6 +447,7 @@ holding export options.
;; title page
(format %s id='title-slide' class='slide'
(plist-get info :html-container))
+ ;; TODO: format-spec isn't great for missing details.
(format-spec org-deck-title-slide-template (org-html-format-spec info))
(format /%s (plist-get info :html-container))
;; toc page
diff --git a/contrib/lisp/ox-s5.el b/contrib/lisp/ox-s5.el
index b003919..8b28692 100644
--- a/contrib/lisp/ox-s5.el
+++ b/contrib/lisp/ox-s5.el
@@ -174,6 +174,7 @@ or an empty string.
(defcustom org-s5-title-slide-template
h1%t/h1
+h2%s/h2
h2%a/h2
h3%e/h3
h4%d/h4
@@ -329,6 +330,7 @@ holding export options.
;; title page
(format %s id='title-slide' class='slide'
(plist-get info :html-container))
+ ;; TODO: format-spec isn't great for missing details.
(format-spec org-s5-title-slide-template (org-html-format-spec info))
(format /%s (plist-get info :html-container))
;; table of contents.
diff --git a/lisp/ox-ascii.el b/lisp/ox-ascii.el
index 5711b53..4f6ecbe 100644
--- a/lisp/ox-ascii.el
+++ b/lisp/ox-ascii.el
@@ -121,7 +121,8 @@
org-ascii-filter-comment-spacing)
(:filter-section . org-ascii-filter-headline-blank-lines))
:options-alist
- '((:ascii-bullets nil nil org-ascii-bullets)
+ '((:subtitle SUBTITLE nil nil space)
+(:ascii-bullets nil nil org-ascii-bullets)
(:ascii-caption-above nil nil org-ascii-caption-above)
(:ascii-charset nil nil org-ascii-charset)
(:ascii-global-margin nil nil org-ascii-global-margin)
@@ -969,9 +970,15 @@ INFO is a plist used as a communication channel.
;; Links in the title will not be resolved later, so we make
;; sure their path is located right after them.
(info (org-combine-plists info '(:ascii-links-to-notes nil)))
- (title (if (plist-get info :with-title)
- (org-export-data (plist-get info :title) info)
- ))
+ (with-title (plist-get info :with-title))
+ (title (org-export-data
+ (when with-title (plist-get info :title)) info))
+ (subtitle (org-export-data
+ (when with-title
+ (org-element-parse-secondary-string
+ (or (plist-get info :subtitle) )
+ (org-element-restriction 'keyword)))
+ info))
(author (and (plist-get info :with-author)
(let ((auth (plist-get info :author)))
(and auth (org-export-data auth info)
@@ -1014,8 +1021,12 @@ INFO is a plist used as a communication channel.
(let* ((utf8p (eq (plist-get info :ascii-charset) 'utf-8))
;; Format TITLE. It may be filled if it is too wide,
;; that is wider than the two thirds of the total
[O] [ox-ascii, bug?] different spacing between title author
Hi, Newlines behave differently when using utf8 and other encodings, e.g. between the top line and the title (which is fine), but also between title and author, which I dislike a lot. I don't know if this is a features. Example: #+title: title #+author: author utf8 output with 2 newlines between title and author and no line between top line and title. TITLE author Ascii output with a single newline between title and author. Much nicer. TITLE author —Rasmus -- This is the kind of tedious nonsense up with which I will not put
Re: [O] Config best practices?
Marcin Borkowski mb...@wmi.amu.edu.pl writes: On 2015-03-20, at 10:07, Sebastien Vauban sva-n...@mygooglest.com wrote: Hello Marcin, Marcin Borkowski wrote: I'm wondering what people do to keep the configuration of their Org files in order. I usually have something like * export options :noexport: # whatever. But in e.g. ox-koma-letter I'd just have * attachments and export options :after-letter: #+begin_latex % Enclosure commands #+end_latex # whatever Generally, I try to minimize the number of (i) hacks outside of org-core (e.g. :ignoreheading:); (ii) number of headings without exported content. —Rasmus -- And I faced endless streams of vendor-approved Ikea furniture. . .
Re: [O] [bug?, ox-latex] creator not commented out
Hello, Rasmus ras...@gmx.us writes: In ox-latex :creator is inserted according to ;; Creator. (and (plist-get info :with-creator) (concat (plist-get info :creator) \n)) Is it on purpose that if :with-creator is non-nil and :creator is the default value, then it's inserted in the pdf, i.e. without being prefixed with %? See 16cea3d7b74e34945355cf434a684890f4c52cb2. Regards, -- Nicolas Goaziou
Re: [O] [ox, patch] Add #+SUBTITLE
Very nice, thanks! On 3/20/2015 10:26 PM, Marcin Borkowski wrote: On 2015-03-21, at 00:23, Rasmus ras...@gmx.us wrote: This patch adds #+SUBTITLE to a couple of backends. This property is WDTY? +1 Best, -- Melanie BACOU International Food Policy Research Institute Snr. Program Manager, HarvestChoice E-mail m.ba...@cgiar.org Visit www.harvestchoice.org
Re: [O] Config best practices?
On 2015-03-20, at 10:07, Sebastien Vauban sva-n...@mygooglest.com wrote:
Hello Marcin,
Marcin Borkowski wrote:
I'm wondering what people do to keep the configuration of their Org
files in order.
I'm not sure to correctly grasp your objective. Could you restate it?
Sure.
Where do you put things like
#+OPTIONS: toc:nil
or
#+SEQ_TODO: TODO | DONE
or
#+LATEX_HEADER: \newcommand{\eps}{\varepsilon}
?
I use a dedicated top-level headline, with a COMMENT keyword, but
I started to think that a :noexport: tag might be a better idea.
Are there any advantages of one over the other, or other approaches
altogether?
I can tell you they aren't isomorphic... The noexport tag simply says
don't export this subtree. The COMMENT keyword adds don't run any
Babel code block in there.
So I guess that – since the lines with options etc. are not exported
anyway – that using a :noexport: tag might be a better idea. Am I right?
The reason I'm asking is that I'm tweaking my org-one-to-many utility
so that it propagates the config to all the generated files.
Still not that clear to me. Maybe an ECM would clarify your request?
As you wish. This is what I usually do.
--8---cut here---start-8---
* Headline
* Another one
** Subheadline
* COMMENT Config
#+LATEX_HEADER: \newcommand{\eps}{\varepsilon}
#+SEQ_TODO: TODO | DONE CANCEL
#+OPTIONS: toc:nil
--8---cut here---end---8---
Best regards,
Seb
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
Re: [O] [ox, patch] Add #+SUBTITLE
On 2015-03-21, at 00:23, Rasmus ras...@gmx.us wrote: This patch adds #+SUBTITLE to a couple of backends. This property is WDTY? +1 Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University
Re: [O] Problems with habit graph in the master branch
Bernt Hansen writes: Hi, I tried out the master branch today and the habit graph seems to be broken. Habits display as normal repeating tasks in commit 40f2b88 (Open outer link on nested links, 2014-11-20) and work normally in commit 7429f35 (Merge branch 'maint', 2014-10-22) Sorry I don't have time to track down the problem commit at the moment. Regards, Bernt org-habit graph also not rendering here in master.
[O] Possible bug: Can not search for text in links - only description
Hi I got an error as follow when I tried to export: , | org-babel-exp process R at line 5495... | Evaluation of this R code-block is disabled. | user-error: Unable to resolve link *uLELFit ` I thought OK - I'll search for uLELFit and just fix this link - but I could do what I wanted, I did not manage to find the link. I figured out that I can not search for text in the link. Thins is quite annoying, especially as I even thought of opening the file in another texteditor, search for the string, and save it again. As an example: if this link is in an org-mode file, A search for exa does not return any results. [[*Examples][Link to exp]] Is this a problem on my side? , | Org-mode version 8.3beta (release_8.3beta-927-ge0b19d @ /Users/rainerkrug/.emacs.d/org-mode/lisp/) | GNU Emacs 24.4.1 (x86_64-apple-darwin14.0.0, Carbon Version 157 AppKit 1343.16) of 2015-02-02 on Rainers-MacBook-Pro-4.local ` Thanks, Rainer -- Rainer M. Krug email: Raineratkrugsdotde PGP: 0x0F52F982 signature.asc Description: PGP signature
Re: [O] Possible bug: Can not search for text in links - only description
Richard Lawrence wrote: Rainer M Krug rai...@krugs.de writes: I figured out that I can not search for text in the link. Thins is quite annoying, especially as I even thought of opening the file in another texteditor, search for the string, and save it again. As an example: if this link is in an org-mode file, A search for exa does not return any results. [[*Examples][Link to exp]] Is this a problem on my side? No, I confirm that that's how it works for me, too. I am not sure if this counts as a bug or not, so someone else should still address this question. Maybe this is the desired behavior, given that the link text is hidden? Or maybe it's just not possible to search in hidden text? There's a less-drastic solution than switching to another editor though! You can just turn off Org mode...try M-x fundamental-mode, then run the search. M-x visible-mode is your friend here. Best regards, Seb -- Sebastien Vauban
Re: [O] Possible bug: Can not search for text in links - only description
Hi Rainer, Rainer M Krug rai...@krugs.de writes: I figured out that I can not search for text in the link. Thins is quite annoying, especially as I even thought of opening the file in another texteditor, search for the string, and save it again. As an example: if this link is in an org-mode file, A search for exa does not return any results. [[*Examples][Link to exp]] Is this a problem on my side? No, I confirm that that's how it works for me, too. I am not sure if this counts as a bug or not, so someone else should still address this question. Maybe this is the desired behavior, given that the link text is hidden? Or maybe it's just not possible to search in hidden text? There's a less-drastic solution than switching to another editor though! You can just turn off Org mode...try M-x fundamental-mode, then run the search. Best, Richard
Re: [O] Possible bug: Can not search for text in links - only description
On Fri, Mar 20, 2015 at 9:44 AM, Rainer M Krug rai...@krugs.de wrote: Hi I got an error as follow when I tried to export: , | org-babel-exp process R at line 5495... | Evaluation of this R code-block is disabled. | user-error: Unable to resolve link *uLELFit ` I thought OK - I'll search for uLELFit and just fix this link - but I could do what I wanted, I did not manage to find the link. I figured out that I can not search for text in the link. `org-toggle-link-display' is very helpful here. See [1] for a discussion of the patch and new behavior. It is perhaps worth considering to change the error message to show the link description (when it exists) rather than the link itself to make it easier to find the bad link. Regards, Jake [1] http://comments.gmane.org/gmane.emacs.orgmode/90891
[O] fontenc makes pdf non-searchable
Hi all,
I'm using org-mode to write a paper and export it to a pdf. It compiles just
fine.
However, when opening the experted pdf (with evince or okular) and searching
for a word, the output from the search function is a list of words with
apparently incorrect character encoding.
I get the same result when compiling directly the exported tex file. However,
if I remove the line:
\usepackage[T1]{fontenc}
the compiled pdf becomes correctly interpreted by the search function.
According to the documentation of the org-article latex class, There
is no facility to disable loading fontenc.
What should I do to make the pdf searchable with the org exporter ?
Thanks,
Martin
Re: [O] Config best practices?
Marcin Borkowski mb...@wmi.amu.edu.pl writes:
On 2015-03-20, at 10:07, Sebastien Vauban sva-n...@mygooglest.com wrote:
Hello Marcin,
Marcin Borkowski wrote:
I'm wondering what people do to keep the configuration of their Org
files in order.
I'm not sure to correctly grasp your objective. Could you restate it?
Sure.
Where do you put things like
#+OPTIONS: toc:nil
or
#+SEQ_TODO: TODO | DONE
or
#+LATEX_HEADER: \newcommand{\eps}{\varepsilon}
?
I use a dedicated top-level headline, with a COMMENT keyword, but
I started to think that a :noexport: tag might be a better idea.
Are there any advantages of one over the other, or other approaches
altogether?
I can tell you they aren't isomorphic... The noexport tag simply says
don't export this subtree. The COMMENT keyword adds don't run any
Babel code block in there.
COMMENT also says that the whole subtree is not to be exported according
to the doc:
(info (org) Comment lines)
Has that changed?
So I guess that – since the lines with options etc. are not exported
anyway – that using a :noexport: tag might be a better idea. Am I right?
The reason I'm asking is that I'm tweaking my org-one-to-many utility
so that it propagates the config to all the generated files.
Still not that clear to me. Maybe an ECM would clarify your request?
As you wish. This is what I usually do.
* Headline
* Another one
** Subheadline
* COMMENT Config
#+LATEX_HEADER: \newcommand{\eps}{\varepsilon}
#+SEQ_TODO: TODO | DONE CANCEL
#+OPTIONS: toc:nil
Yes, but why do you do that? What are you trying to accomplish? What
does keeping the configuration in order mean?
I sometimes use a Setup heading marked with COMMENT, so it does not get
exported. I never put babel stuff in there so I haven't worried about
that, but if Seb is correct that it prevents babel from evaluating
things in the subtree, that's a bonus. If you are just trying to
(mostly) hide it from view, add an :ARCHIVE: tag to the heading.
But most of the time I have them at the top of the file in plain view.
--
Nick
Re: [O] [proposal] timezone-aware timestamps enhancement
On 2015-03-20 at 05:40, Randomcoder randomcod...@gmail.com wrote: On Wed, Mar 18, 2015 at 02:09:31PM -0400, Ken Mankoff wrote: I have a solution that works quite well outside of Org. Apple Calendar supports timezones plus a floating option. I use Org for all my floating events - local to the computer and me, whatever TZ we're in. I haven't found a way to put TZ-specific events into Org. You said above you're using iCal (do you mean, Google Calendar or Apple Calendar?). I'd be interested in setting this up as well, which one should I be using ? I use Apple. There is integration for Apple - Org, Org - Apple, Google - Org, and Org - Google. At this point in time I'm using Org-Mode's agenda to view events. Should I try to sync them up with my phone and if so what is the recommended way to go ? Depends on what you want. You could view everything in MobileOrg. Or export to a calendar and then view that. -k.
Re: [O] Possible bug: Can not search for text in links - only description
hmm: === search-invisible is a variable defined in `isearch.el'. Its value is open Documentation: If t incremental search/query-replace can match hidden text. A nil value means don't match invisible text. When the value is `open', if the text matched is made invisible by an overlay having an `invisible' property and that overlay has a property `isearch-open-invisible', then incremental search will show the contents. (This applies when using `outline.el' and `hideshow.el'.) ... === -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com Ramsay's disease DOES progress. MANY people have died from it. And ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] Possible bug: Can not search for text in links - only description
org-show-context-detail may also be relevant: org-show-context-detail is a variable defined in `org.el'. Its value is ((isearch . lineage) (bookmark-jump . lineage) (default . ancestors)) Documentation: Alist between context and visibility span when revealing a location. Some actions may move point into invisible locations. As a consequence, Org always expose a neighborhood around point. How much is shown depends on the initial action, or context. Valid contexts are agenda when exposing an entry from the agenda org-goto when using the command `org-goto' (C-c C-j) occur-tree when using the command `org-occur' (C-c / /) tags-tree when constructing a sparse tree based on tags matches link-searchwhen exposing search matches associated with a link mark-goto when exposing the jump goal of a mark bookmark-jump when exposing a bookmark location isearchwhen exiting from an incremental search defaultdefault for all contexts not set explicitly ... but I haven't followed through to see exactly how to use it.
Re: [O] Possible bug: Can not search for text in links - only description
On Fri, 20 Mar 2015, Ken Mankoff wrote: It would be nice to be able to search in links without extra work to change modes. Without this, you cannot even search for a cite key! You *can* search in links without changing modes. menu-bar edit search search-forward Exa RET runs nonincremental-search-forward on Exa and finds Rainier's `*Example' if point preceeds it. M-x occur RET Exa RET finds the link, too. Chuck -k. Please excuse brevity. Sent from pocket computer with tiny non-haptic feedback keyboard. On Mar 20, 2015, at 11:38, Jacob Gerlach jacobgerl...@gmail.com wrote: On Fri, Mar 20, 2015 at 9:44 AM, Rainer M Krug rai...@krugs.de wrote: Hi I got an error as follow when I tried to export: , | org-babel-exp process R at line 5495... | Evaluation of this R code-block is disabled. | user-error: Unable to resolve link *uLELFit ` I thought OK - I'll search for uLELFit and just fix this link - but I could do what I wanted, I did not manage to find the link. I figured out that I can not search for text in the link. `org-toggle-link-display' is very helpful here. See [1] for a discussion of the patch and new behavior. It is perhaps worth considering to change the error message to show the link description (when it exists) rather than the link itself to make it easier to find the bad link. Regards, Jake [1] http://comments.gmane.org/gmane.emacs.orgmode/90891 Charles C. Berry Dept of Family Medicine Public Health cberry at ucsd edu UC San Diego / La Jolla, CA 92093-0901 http://famprevmed.ucsd.edu/faculty/cberry/
Re: [O] Possible bug: Can not search for text in links - only description
It would be nice to be able to search in links without extra work to change modes. Without this, you cannot even search for a cite key! -k. Please excuse brevity. Sent from pocket computer with tiny non-haptic feedback keyboard. On Mar 20, 2015, at 11:38, Jacob Gerlach jacobgerl...@gmail.com wrote: On Fri, Mar 20, 2015 at 9:44 AM, Rainer M Krug rai...@krugs.de wrote: Hi I got an error as follow when I tried to export: , | org-babel-exp process R at line 5495... | Evaluation of this R code-block is disabled. | user-error: Unable to resolve link *uLELFit ` I thought OK - I'll search for uLELFit and just fix this link - but I could do what I wanted, I did not manage to find the link. I figured out that I can not search for text in the link. `org-toggle-link-display' is very helpful here. See [1] for a discussion of the patch and new behavior. It is perhaps worth considering to change the error message to show the link description (when it exists) rather than the link itself to make it easier to find the bad link. Regards, Jake [1] http://comments.gmane.org/gmane.emacs.orgmode/90891
Re: [O] [patch, koma-letter] Change of subject behavior
Nicolas Goaziou m...@nicolasgoaziou.fr writes: AFAIC, you can push the patches, when the above is fixed. Thank you. Pushed: 304a5cb ox-koma-letter: Interpret #+SUBJECT. a795d9e ox-koma-letter: Stricter subject inference c4d4e5e ox-koma-letter: Tiny refactor —Rasmus -- Bang bang
Re: [O] How to represent Emacs keystrokes in Org?
Marcin Borkowski wrote:
Hi there,
it seems that reviving old threads is my new hobby;-).
On 2014-11-29, at 22:58, Marcin Borkowski mb...@wmi.amu.edu.pl wrote:
On 2014-11-29, at 22:53, Marcin Borkowski wrote:
On 2014-11-24, at 19:38, Rasmus wrote:
Marcin Borkowski mb...@wmi.amu.edu.pl writes:
Hello,
I'm writing (in Org) a text on Emacs usage. How to
correctly/canonically represent keystrokes, like C-x RET f?
Currently, I use =C-x RET f=; are there any alternatives?
That's what I'd do. Or ~C-x RET f~. You could also use a macro, if you
want it to me be more semantic (I hope I use this word correctly).
This might seem a good idea, but how do I do it? (See below for
a concrete problem statement.)
Houston, we've got a problem. What about =M-,=? Somehow it seems not
to be interpreted in the right way: it does not get fontified correctly,
nor does export in the right way. What can I do about it? I found
about org-emphasis-regexp-components, is it the only way? Also, how do
I reload Org without restarting Emacs? (I am an Emacs geek and I try to
beat my record of emacs-uptime, you know. ;-) )
Wow, I got an idea, and it worked. Here's an excerpt from `C-u C-x ='
at my solution;-):
position: 11859 of 16051 (74%), column: 253
character: (displayed as ) (codepoint 8205, #o20015, #x200d)
preferred charset: unicode (Unicode (ISO10646))
code point in charset: 0x200D
syntax: . which means: punctuation
to input: type C-x 8 RET HEX-CODEPOINT or C-x 8 RET NAME
buffer code: #xE2 #x80 #x8D
file code: #xE2 #x80 #x8D (encoded by coding system utf-8-unix)
display: by this font (glyph code)
xft:-unknown-Phetsarath
OT-normal-normal-normal-*-17-*-*-*-*-0-iso10646-1 (#x120)
Character code properties: customize what to show
name: ZERO WIDTH JOINER
A bit ugly trick, but works. What are the opinions?
After a while I have to say that my opinion is strongly negative: this
breaks LaTeX export. (LaTeX doesn’t like some unicode characters, it
turns out.) Also, this was really an ugly hack...
So, here is my problem: how to represent a key like M-, or
e.g. a sequence \, (important in regexps) as “code” or “verbatim stuff”
in org-mode? Neither =\,= nor ~\,~ work, of course. Also, I’d like
this to be backend-agnostic, so \texttt{M-,} doesn’t really work.
I'm thinking at something like this (partially untested):
--8---cut here---start-8---
#+LATEX_HEADER: \usepackage{menukeys}
#+LATEX_HEADER: \let\ORIkeys\keys
#+LATEX_HEADER: \renewcommand{\keys}[1]{\ORIkeys{\texttt{#1}}}
#+LATEX_HEADER: \newcommand{\repeatedkeys}[1]{\keys{\textcolor{gray}{#1}}}
#+MACRO: kbd \keys{$1}
--8---cut here---end---8---
Of course, the macro would have to be improved to work at least (in my
case) in both HTML and LaTeX, by using the @@latex:...@@ construct.
What is the rationale behind forbidding the comma as the “border”
character in org-emphasis-regexp-components? Should I change this
variable in my setup or is there a more general way to convince Org that
I really want verbatim/code snippets like =\,=?
I share your point about a better `org-emphasis-regexp-components' by
default, which would work in 99.9% of the cases.
Best regards,
Seb
--
Sebastien Vauban
Re: [O] Problems with habit graph in the master branch
Hello, Christopher Allan Webber cweb...@dustycloud.org writes: org-habit graph also not rendering here in master. Could you show an ECM? Regards, -- Nicolas Goaziou
