Re: [O] Reftex in Org-Mode exporting and recognizing figures or equations
Aloha Jeffrey,
Jeffrey Spencer writes:
> 1) I was wondering if anyone has got the reftex feature of easily
> recognizing the figures and equations to insert as a ref command to work in
> org-mode.
I'm not aware of this being done.
>
> 2) Also I had seen on a website that you can use the command to get
> org-mode type citations. This seems to export to latex as a \ref command
> with citep in the middle (eg. \ref{citep}).
> (reftex-set-cite-format
> "[[citep][%l]]")
> This doesn't seem to work for me but maybe I'm doing something wrong.
There are some examples of how to manage citations in Org mode here:
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-17-2
I'm really enjoying ebib in this regard. It recognizes both Org mode
and LaTeX mode documents, so is ready to work with me in both of my
writing environments.
hth,
Tom
> 1) I was wondering if anyone has got the reftex feature of easily recognizing
> the figures and equations to insert as a ref command to work in org-mode.2)
> Also I had seen on a website that you can use the command to get org-mode
> type citations. This seems to export to latex as a \ref command with citep in
> the middle (eg. \ref{citep}).
>
> (reftex-set-cite-format "[[citep][%l]]")This doesn't seem to work for
> me but maybe I'm doing something wrong.
--
Thomas S. Dye
http://www.tsdye.com
[O] Reftex in Org-Mode exporting and recognizing figures or equations
1) I was wondering if anyone has got the reftex feature of easily
recognizing the figures and equations to insert as a ref command to work in
org-mode.
2) Also I had seen on a website that you can use the command to get
org-mode type citations. This seems to export to latex as a \ref command
with citep in the middle (eg. \ref{citep}).
(reftex-set-cite-format
"[[citep][%l]]")
This doesn't seem to work for me but maybe I'm doing something wrong.
[O] [BUG] Traceback on Org-Export
Guys:
I pulled the latest and greatest from Git after I uploaded by changes
on the exporter and I got the following trace during import of org-export.
??
Luis
Debugger entered--Lisp error: (void-variable org-outline-regexp-bol)
(concat "^[ ]*$" "\\|" org-outline-regexp-bol "\\|" "^[ ]*#\\+" $
(defconst org-element-paragraph-separate (concat "^[ ]*$" "\\|" org-o$
eval-buffer(#> nil "/opt/home/papo/.emacs.d/org/lisp$
load-with-code-conversion("/opt/home/papo/.emacs.d/org/lisp/org-elemen$
require(org-element)
eval-buffer(#> nil "/opt/home/papo/.emacs.d/org/cont$
load-with-code-conversion("/opt/home/papo/.emacs.d/org/contrib/lisp/or$
require(org-export)
eval-buffer(#> nil "/opt/home/papo/.emacs.d/org/cont$
load-with-code-conversion("/opt/home/papo/.emacs.d/org/contrib/lisp/or$
require(org-e-groff)
eval-buffer(# nil "/opt/home/papo/.emacs" nil t) ; Re$
load-with-code-conversion("/opt/home/papo/.emacs" "/opt/home/papo/.ema$
load("~/.emacs" t t)
#[nil "^H\205\264^@ \306=\203^Q^@\307^H\310Q\2027^@ \311=\2033^@\312$
command-line()
normal-top-level()
--
Luis R. Anaya
papo anaya aroba hot mail punto com
"Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
[O] [ANN] Org-e-groff.el improvements.
Hi: I know that I've not said much of late, but I'm not sitting idle. The following new features added to the Groff Exporter. - Ability to handle long tables. Long tables were being truncated, now there is an option to tell the export when tables contain very long cells. The reason for this to be an option is because of discrepancies in the way TBL handles formatting. - Ability to automatically generate reference lists Using [fn:rl123] will not create a footnote, but a reference. The reference is listed at the end in the table of contents. - Ability to perform special processing in paragraph This was needed for advanced text processing, for instance, to create Drop Capitals. The reason why Drop Capitals are not a feature is because they are not available in the MM macro set. The use of a specialized macro is needed. However, MOM macros include Drop Capitals Macros, but I've not started porting from MM to MOM yet. - Ability to disable captions. This was needed for special circunstances in which a caption is not desired. For Tables, Figures and Exhibits (programs) adding a :disable-caption t in the #+ATTR_GROFF: line disables it. - Ability to process special characters. This was needed to provide correct representation of Copyright, Trademark and Registered marks. - Improved table handling Improvements were made during while fixing the long tables format. Showcases: Source: http://ppl.ug/Q60uBaHOrw4/ PDF Output: http://ppl.ug/C9HvWdjMnDI/ Source: http://ppl.ug/RpTrZY73eSg/ PDF Output: http://ppl.ug/p_d-STCegXk/ Availability: Available in GitHub/emacs_utils and in Org Mode Git. QA Note: - Regression test suite passed. - No issues detected while exporting meeting notes. -- Luis R. Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
[O] [BUG] turn-on-org-cdlatex
Hi,
It would seem there is a bug in turn-on-org-cdlatex whenever _ or ^ is
called. And perhaps others.
To reproduce:
bash> emacs -q
In *scratch*
#+begin_src emacs-lisp
;; adjust the two following lines to your system
(load-file "/usr/share/emacs/site-lisp/auctex/texmathp.el")
(load-file "~/.emacs.d/elpa/cdlatex-4.0/cdlatex.el")
(require 'cdlatex)
(add-hook 'org-mode-hook 'turn-on-org-cdlatex)
(switch-to-buffer "test.org")
#+end_src
Then
M-x org-mode
#+begin_src org
* test
insert `$' then `x' then `_' then `1', i.e. $x_1$
#+end_src
I get the following backtrace
Debugger entered--Lisp error: (void-variable last-command-char)
(char-to-string last-command-char)
(concat (char-to-string last-command-char) "{")
(string= (buffer-substring (max (point-min) (- (point) 2)) (point)) (concat
(char-to-string last-command-char) "{"))
(if (string= (buffer-substring (max (point-min) (- (point) 2)) (point))
(concat (char-to-string last-command-char) "{")) (progn (backward-char 1)
(insert last-command-char) (forward-char 1)) (insert last-command-char) (insert
"{}") (forward-char -1))
(if (cdlatex-number-of-backslashes-is-odd) (insert last-command-char) (if
(not (texmathp)) (cdlatex-dollar)) (if (string= (buffer-substring (max
(point-min) (- (point) 2)) (point)) (concat (char-to-string last-command-char)
"{")) (progn (backward-char 1) (insert last-command-char) (forward-char 1))
(insert last-command-char) (insert "{}") (forward-char -1)))
cdlatex-sub-superscript()
call-interactively(cdlatex-sub-superscript)
org-cdlatex-underscore-caret(nil)
call-interactively(org-cdlatex-underscore-caret nil nil)
System:
GNU Emacs 24.1.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 3.4.4)
of 2012-08-02 on rasmus
Org-mode version 7.8.11 (release_7.8.11-338-gecba55 @
/usr/share/emacs/site-lisp/org/)
--
In theory, practice and theory are the same. In practice they are not
Re: [O] Following references to labelled images
Hi Nicolas, Nicolas Goaziou writes: > Hello, > > Andreas Leha writes: > >> it seems to be not possible to follow references to images (for >> example) as here: >> >> There is a Figure [[fig_test_C_c_C_o]] >> >> #+caption: Try to get to this figure via C-c C-o on the reference >> #+label: fig_test_C_c_C_o >> [[foo.png]] > > Use NAME instead of LABEL. > As easy as that! Thanks a lot. Regards, Andreas
Re: [O] Following references to labelled images
Hello, Andreas Leha writes: > it seems to be not possible to follow references to images (for > example) as here: > > There is a Figure [[fig_test_C_c_C_o]] > > #+caption: Try to get to this figure via C-c C-o on the reference > #+label: fig_test_C_c_C_o > [[foo.png]] Use NAME instead of LABEL. Regards, -- Nicolas Goaziou
Re: [O] Managing Images with Org-mode?
* Karl Eichwalder wrote:
> Bastien writes:
>
>>> http://www.flickr.com/photos/keichwa/7649891572
>> Looks nice.
>>
>> How did you put the thumbnails in the Org mode file?
>
> Once I understood the differences between "inline images" (images
> without a description) and "linked images", it was easy:
>
> [[file:path_to_inline_image__thumbnail.png]]
Inspired by your posting, I wrote this short yasnippet in case I
want to use something similar in future:
,[ ~/.snippets/tls ]
| name : Insert a table with files of a folder including links
| # --
| #+BEGIN_SRC sh
| PATTERN='${1:*.jpg}'
| MYFOLDER='${2:$HOME/}'
| cd \${MYFOLDER}; MYPWD=\`pwd\`; for file in \`ls -1 \${PATTERN}\`; do echo
'-[['\$MYPWD'/'\$file']]'; done
| #+END_SRC
`
Obviously, this does not work this way with Windows.
There might be room for improvement - please follow up if you
optimized it :-)
One thing: the dash in front of the '[[' is mandatory. Well, it does
not need to be a dash though. Any other normal character (non-empty,
not space) works as well. I did not quite understand why and did not
pay further attention.
The script above results in an Org-mode *table*. To me this was a
minor issue.
Related to this topic: C-c C-x C-v (org-toggle-inline-images) is of
interest for you. On a per-file-basis this is: #+STARTUP inlineimages
--
Karl Voit
[O] Following references to labelled images
Hi all, it seems to be not possible to follow references to images (for example) as here: There is a Figure [[fig_test_C_c_C_o]] #+caption: Try to get to this figure via C-c C-o on the reference #+label: fig_test_C_c_C_o [[foo.png]] I do not recall whether this has been possible at some time, but it seems like a missing feature to me. Is there another way to jump to the referenced label from the reference, that I am missing? Regards, Andreas
[O] test-ob-sh/session
I'm currently seeing a problem with this test (only on Win7, both NTEmacs and Cygwin). The test just hangs and never finishes. All my attempts to have it fail in the same way in an interactive sessions were fruitless. However, it seems that the first time a session is initiated, it does not start at all. The second time it then works as expected. Why Emacs hangs when it gets there in batch mode I can't see... Incidentally, sh tests will run even when not explicitly configured, which seems odd since I can't find any code that loads ob-sh either directly or through autoloads and thus the guard code at the top of the test file should leave those tests undefined. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] Problem with commented LaTeX header lines
Hi Nicolas Nicolas Goaziou writes: > Hello, > > Andreas Leha writes: > >> I started to get problems with commented latex headers. All headers >> after the commented line seem to be ignored. Is this intended / am I >> using the comments wrongly? > > This is not intended. It is a parsing bug introduced with new comment > syntax. This should be fixed now. > I can confirm the fix here. Thanks a lot! Regards, Andreas
Re: [O] Problem with commented LaTeX header lines
Hello, Andreas Leha writes: > I started to get problems with commented latex headers. All headers > after the commented line seem to be ignored. Is this intended / am I > using the comments wrongly? This is not intended. It is a parsing bug introduced with new comment syntax. This should be fixed now. Thank you for reporting this. Regards, -- Nicolas Goaziou
Re: [O] Problem with commented LaTeX header lines
Hi Bastien,
thanks for looking into this!
>
> Please always tell what exporter you are using.
>
I did mention this:
> > Test with new exporter - no cmbright:
^^^
I am sorry, if this was not explicit enough. (Is "new exporter" the
correct name?)
> Your example works with the default LaTeX exporter.
>
> With the new exporter, you don't get \usepackage{cmbright} because
> you explicitely asked not to export this subtree with :noexport:.
>
I do not agree, because it works as expected, if I remove the comment
sign:
,
| #+TITLE: Commented LaTeX headers
|
|
| * Try to export this subtree
| With some text.
|
| And a second paragraph.
|
|
| ** And a section
| With some text.
|
| * Options:noexport:
| ** LaTeX Options
| #+LATEX_HEADER: \usepackage{hyperref}
| #+LATEX_HEADER: \usepackage{tikz}
| #+LATEX_HEADER: \usepackage{cmbright}
`
> To me the new exporter is right here.
To me loosing that possibility would be hard, as my latex_header
sections tend to grow really long, so that I would not
be happy to move them to the top. This has always been one of the
really nice things in my opinion, that I can hide all this technical
information in a non-exported subtree.
Regards,
Andreas
Re: [O] Suggested change to Manual 3.5.9 example table
On 8/2/2012 11:41 AM, Bastien wrote: Hi Charles, Charles writes: As to submitting a patch - Thank you but I have to pass, even for such a tinychange. Downloading, installing and learning git is a project slated for later this year. You don't have to learn git. C-x C-f [/...]org.texi C-x v v RCS [Make the change] C-x v = [Save the diff and send it to the list.] If you don't plan to do it, please let us know, so that someone else can send a patch. Thanks, Bastien, Thanks for the lesson. I'll give it a try. Charlie
[O] Templates for cloning
Hi all, Is there a way to create a template structure for cloning? The main purpose would be to create a shell or structure that is easy to replicate, such as a workflow, etc. This shell, etc would not need any hard-coded dates, but could simply have offsets for sub-items whose due-dates or start dates are relative to a single start date. For example, I'd like to have this: * Some Project ** Plan Project ** Step 1 ** Step 2 ** Project Due This would be cool, because 1) You wouldn't see this template in the agenda, because the dates aren't hard-coded 2) You could be prompted for the start date when you clone this template, and all the dates would then be created from that start date 3) When cloning this template, you wouldn't have to calculate the delta between the template's date and the initial start date that you plan for the clone of this template Does anyone know of a way to do this? - I could keep this template in another directory or re-name it as .TXT so that the agenda wouldn't pick up the template's fake start dates, but this seems hacky. Thanks --Nate
[O] Babel give "Marker does not point anywhere" first run of LaTeX export; subsequent are fine
When I open an org file the first time and export to PDF via LaTeX, I get the error "Marker does not point anywhere" and the LaTeX export quits. Running it again without doing anything else succeeds, and all subsequent exports work fine. This is on Windows 7. Thoughts? John
Re: [O] Shouldn't comment-region protect from export ?
Hi William, William LÉCHELLE writes: > Using org-mode for export (to pdf), I find myself using comment-region often > enough, in sections meant to be exported, on indented text lines (e.g. for > drafting). This inserts "# " at the "beginning" of the line, after the > indentation, thus not achieving what I wanted comment-region to do > (i.e. "don't export this"). This is fixed now, thanks. -- Bastien
Re: [O] org-html: subtree specific footnote references
Hi Suhail, I have accepted the patch. I added a TINYCHANGE cookie at the end of the git commit message: this is requested for tiny changes made by people who did not sign the FSF papers. Suhail Shergill writes: > *if* this patch makes sense, i'm willing to submit a patch for > org-e-html.el. The patch makes sense but is still a bit hackish. I accepted it because the functionality is useful in some cases and because it only affects org-html.el, which days are counted. > does anyone have any views? My view is that org-e-html.el should also make sure that we always have unique ids for all the footnotes of the current files, even when we export only part of it. This is not a trivial change though, because org-export.el has to change the way it retrieves the footnote number. Can you have a look at this? > does this patch 'make sense', and is this the right place for it? Yes, it is the right place for such patches. Thanks, -- Bastien
Re: [O] Suggested change to Manual 3.5.9 example table
Hi Charles, Charles writes: > As to submitting a patch - Thank you but I have to pass, even for such a > tinychange. Downloading, installing and learning git is a project slated > for later this year. You don't have to learn git. C-x C-f [/...]org.texi C-x v v RCS [Make the change] C-x v = [Save the diff and send it to the list.] If you don't plan to do it, please let us know, so that someone else can send a patch. Thanks, -- Bastien
Re: [O] capture template question
On Thu, Aug 02 2012, Bastien wrote: > Hi Eric, > > Eric Abrahamsen writes: > >> Rather than trying to add various ways of citing links, perhaps it would >> be nice to have a format code for the literal link to the thing under >> point at time of capture? What I mean is, something like "%l" so I could >> do this: >> >> * EMAIL Respond to [[%l][%:fromname]]%? > > Good idea. You can now use %l to insert this literal link. Brilliant! Thank you. -- GNU Emacs 24.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.24.11) of 2012-08-02 on pellet 7.8.11
Re: [O] Export to Texinfo
Hi Jonathan, Jonathan Leech-Pepin writes: > I've done some further work on the org-e-texinfo exporter and have > gotten it to a point where it should be usable with only a few > shortcomings. thanks *a lot* for this! This is long-time wish from many org-ers, no doubt you will have many testers. Do you want to continue to develop while adding the library to contrib/lisp/? One problem with the version you sent: (org-export-first-sibling-p headline) (org-export-last-sibling-p headline) should be (org-export-first-sibling-p headline info) (org-export-last-sibling-p headline info) With this change I can export files correctly. Another thingy: headlines from level 4 are converted to lists, right? I'm fine with this, as long as the list is not collapsed with a previous one. See the .org and .texi files attached. Thanks again for this great contribution! test-texinfo.org Description: Lotus Organizer test-texinfo.texi Description: TeXInfo document -- Bastien
Re: [O] Problem with commented LaTeX header lines
Hi Andreas,
Andreas Leha writes:
> I started to get problems with commented latex headers.
Please always tell what exporter you are using.
Your example works with the default LaTeX exporter.
With the new exporter, you don't get \usepackage{cmbright} because
you explicitely asked not to export this subtree with :noexport:.
To me the new exporter is right here.
I'd suggest moving #+LATEX_HEADER: \usepackage{cmbright} to the top
of your file if you want it exported with both exporters.
HTH,
--
Bastien
Re: [O] make test on Mac
Hi Eric, Eric Schulte writes: > The `org-test-load' function, which loads of all of the test files, > catches these missing-test-dependency signals and for each one it > creates a dummy test that fails but is expected to fail. These tests > serve to indicate to the user that there are tests which are not being > run. That's the part I overlooked. > Does this all make sense? 100% -- thanks for the detailed explanations! -- Bastien
Re: [O] Feature that org mode needs most
Steinar Bang writes: > I will pull and try the new functionality. Yes -- please let me know. The drawback of this functionality is that it changes things outside of sight, which I don't really like. You get a message, and the subtree of the (possibly distant) clock get unfolded, but perhaps the change can be made more visible -- or "into control". Let me know, -- Bastien
Re: [O] Embed images in formats best suited for HTML and LaTeX export and inline viewing
Brett Viren writes: > So, I'm satisfied now. Thanks for the nudge! I learned something -- you're welcome, -- Bastien
Re: [O] are super-hidden technical blocks required?
If the whole point is to make some properties less visible, why not a solution based on fontification? We could have a user-defined regexp to highlight (or "dim") certain properties. I don't believe in a solution that would change the current flow of cycling through drawers. I feel that's too much. Patch welcome, -- Bastien
Re: [O] capture template question
Hi Eric, Eric Abrahamsen writes: > Rather than trying to add various ways of citing links, perhaps it would > be nice to have a format code for the literal link to the thing under > point at time of capture? What I mean is, something like "%l" so I could > do this: > > * EMAIL Respond to [[%l][%:fromname]]%? Good idea. You can now use %l to insert this literal link. -- Bastien
Re: [O] Introducing Octopress Exporter
Aurélien Aptel writes: > Since it's all static you relying on an external service like > Disqus. I'm not so fond of losing control over user contribution like > that. Besides, the actual service (disqus) is pretty terrible > anyway. I'm always pissed when the comment I sent gets processed in > weird ways yet doesn't do verbatim/code blocks. If the person making the post is paying himself for hosting his website and if the hosting provider charges a price for dynamic pages (cgi/php) then the person could be unwilling to shoulder additional charges. This is particularly so if the person has no commercial interest but only plain colloboration interest. Comments and spam are a pain. Just look at how WikEmacs is getting spammed everday. --
Re: [O] org-mobile : security
Richard Riley writes: > org-mobile allows you to use some form of encryption when pushing to the > MobileOrg directory. Encrypts and works fine. The issue is that the > mobile app has a password setting to unencrypt but there is no > protection on the app itelf meaning anyone can read the org files from > thje mobileorg app itself kind of defeating the object since dropbox has > its own encrption based on id/pasword anyway. Please explain your threat model :-) Seriously, the fact that the org files are available on the phone does not seem any scarier than one's email being available on the phone. I am boggled that you think anything about dropbox security is ok. In my view, the whole point of org-mobile encryption is to put ciphertext only on the webdav server used to transfer between emacs and phone, so that the webdav server does not need to be trusted for confidentiality. It seems unwise to trust dropbox, given the lack of clarity around access to plaintext by dropbox staff, and encryption lets one comfortably use a shared web server whose admins are not cleared to see the private org data. > I realise I can encrypt > org entries myself (I do) using gpg keys but since there is no built in > gpg decryption facility in mobileorg thats hard work (you need to copy > the encrypted entries to oPenGPG which does feature app pin protection and > holds my secret key (which needs a password too)). > > Is there a way to protect the mobileorg app? Or do I need to manually remove > the password from the mobileorg settings each time? It seems like perhaps you want a phone-wide confidentiality solution. pgpasNiuRZFRZ.pgp Description: PGP signature
Re: [O] Introducing Octopress Exporter
Aurélien Aptel gmail.com> writes: > > I've never heard of octopress, interesting. The only thing I don't > like is how comments are handled. Since it's all static you relying on > an external service like Disqus. I'm not so fond of losing control > over user contribution like that. Besides, the actual service (disqus) > is pretty terrible anyway. I'm always pissed when the comment I sent > gets processed in weird ways yet doesn't do verbatim/code blocks. > > On Thu, Aug 2, 2012 at 1:21 AM, Tom Alexander paphus.com> wrote: > > The important changes are all at the bottom of the file. Basically I > > just grab the text before the html preprocessor gets to it and go > > through line-by-line to find the code blocks. > > Have you tried Nicolas Goaziou new parser? org-element.el is a big > improvement for org-mode IMHO. > > Yeah, the whole Disqus comments thing can be a pain, but since the pages are all static its a lot easier on your web server and possibly faster since you don't have a server side language rendering the page. Also, having the posts written mostly in plain HTML (with some special markup for the header and code blocks) its easy for anyone who has written HTML to pick it up, and even easier to use other tools like org-mode to post to it. In terms of org-element, I did look at it when I was writing this, and it looks significantly better, but I was getting errors loading org-mode from the repository at the time. After writing this I learned that apparently master is the development branch for this project, not the stable branch. I might re-write this for the new exporter later since I'm sure the old exporter is on its way out.
Re: [O] babel awk with table input: Code block produced no output.
Hi Greg,
Greg Minshall wrote:
> hi. it appears that a left or right paren in an entry in a table makes
> awk not execute. here's an example (change ":stdin fails" to ":stdin
> works" to see it work). cheers, Greg
>
> #+tblname: fails
> | proto | no c code ||
> | pscl | c code, just fine ||
> | quadprog | (minimal) c code, just fine ||
>
> #+tblname: works
> | proto | no c code ||
> | pscl | c code, just fine ||
> | quadprog | minimal c code, just fine ||
>
> #+begin_src awk :stdin fails
> BEGIN {
> print "starting"
> }
> {
> print $0
> }
> #+end_src
Confirmed.
Though, no idea why.
Best regards,
Seb
--
Sebastien Vauban
[O] babel awk with table input: Code block produced no output.
hi. it appears that a left or right paren in an entry in a table makes
awk not execute. here's an example (change ":stdin fails" to ":stdin
works" to see it work). cheers, Greg
#+tblname: fails
| proto | no c code ||
| pscl | c code, just fine ||
| quadprog | (minimal) c code, just fine ||
#+tblname: works
| proto | no c code ||
| pscl | c code, just fine ||
| quadprog | minimal c code, just fine ||
#+begin_src awk :stdin fails
BEGIN {
print "starting"
}
{
print $0
}
#+end_src
Re: [O] [Assistance Needed] View only prioritized items that have a deadline or or scheduled
François,
Thanks for the help on this, and sorry about the late response. I may have
asked the wrong way, but this solution is exactly what I am looking for.
I use priority, scheduled [start times] and deadlines in the following way;
A tasks need to be done today
B tasks need to be done in the next 14 days
C tasks need to be done in 30 days or more
With each type of task only showing up when scheduled to start and
deadlines only being true deadlines not "fake".
The issue sometimes is that with routine/repeating items that have to be
done a specific day (which are normally an "A" task) I do not want to see
them until they need to be done (based on the scheduled date). So what I
was doing was removing the priority to make them not show up in a view for
mobileorg. Or the next scenario would be something that has a deadline that
I really do not want to see until a determined time (based on the scheduled
start time).
On Wed, Aug 1, 2012 at 5:23 AM, François Allisson wrote:
> Le mardi 31 jui 2012 à 20:48:02 (-0400), Andre Powell a écrit :
> > I was wondering if someone could help me out with the following. I am
> trying to
> > create a custom agenda view that shows me items that have a priority and
> either
> > a scheduled date or deadline. This is what I have tried but it does not
> seem to
> > work.
> >
> > ("x" "Daily Scheduled Task" tags-todo "+PRIORITY={A\\|B\\|C}"
> > ((org-agenda-skip-function (quote (org-agenda-skip-entry-if (quote
> > notscheduled) (quote notdeadline))
> >
> >
> > The ideal situation would be to have task show up that are scheduled to
> begin
> > either today or before today.
> >
> >
> > Thanks in advance for any assistance provided.
> > --
> > Andre
> >
>
> Hi Andre,
>
> I can't help you with your tags-todo view. But your ideal situation
> remembers me more an agenda than a tags-todo view. What about:
>
> ;; Custom agenda-views
> (setq org-agenda-custom-commands
> '(
>
> ;; other custom agenda views
>
> ("x" "Daily Scheduled Task"
> ((agenda ""
> ((org-agenda-span 1)
> (org-agenda-entry-types '(:deadline :scheduled))
> ;; only deadline and scheduled
> (org-deadline-warning-days 0)
> ;; you didn't specified how you wanted your deadline to
> ;; appear. If only today and overdued items, set 0 as
> ;; above; if you want to see them 30 days ahead, set 30; etc.
> ;; By default, scheduled items appear only for today and
> ;; past days (if todo item not done)
> (org-agenda-sorting-strategy (quote ((agenda time-up
> priority-down category-up tag-up
> ;; Set your sorting strategy
> ; other options like (org-agenda-time-grid nil), etc.
>
>
> ))
>
> This should do /almost/ what you want: It shows only deadline and
> scheduled items, and you can sort by priority.
>
> But there is one thing that I do not understand in your request (I do
> not use priorities). Do you have items *with* deadline/schedule date
> *and* no priority, that you don't want to see in your custom agenda
> view? Can you explain me the idea behind?
>
> Because in that case, this would not do the trick. By default, *all*
> items have a priority of B (see org-default-priority). What you could
> decide is to redefine the priority set (org-lowest-priority and
> org-highest-priority) by introducing a priority D, and decide to let
> org-default-priority be D.
>
> Best,
>
> François.
>
--
Andre
[O] org-mobile : security
org-mobile allows you to use some form of encryption when pushing to the MobileOrg directory. Encrypts and works fine. The issue is that the mobile app has a password setting to unencrypt but there is no protection on the app itelf meaning anyone can read the org files from thje mobileorg app itself kind of defeating the object since dropbox has its own encrption based on id/pasword anyway. I realise I can encrypt org entries myself (I do) using gpg keys but since there is no built in gpg decryption facility in mobileorg thats hard work (you need to copy the encrypted entries to oPenGPG which does feature app pin protection and holds my secret key (which needs a password too)). Is there a way to protect the mobileorg app? Or do I need to manually remove the password from the mobileorg settings each time?
Re: [O] Problem with commented LaTeX header lines
> I started to get problems with commented latex headers. All headers > after the commented line seem to be ignored. Is this intended / am I > using the comments wrongly? > > Test with new exporter - no cmbright: Hi, I confirm I get the same behaviour with the latest org (7.8.11-333 and emacs 24.1.50.1). But at first, I could not reproduce it with my "old" org (7.8.11-302). François.
Re: [O] fast todo kw / -> x
Hi Samuel, Samuel Wales writes: > On 7/14/12, Bastien wrote: >> I updated a docstring and a part of the manual to make it >> clearer only letters are supported. > > Thanks, Bastien. :) I appreciate the clarity in the manual. Actually I was wrong. All characters are supported for fast todo selection, except @ / and !. I've fixed the manual and the docstring. -- Bastien
Re: [O] Introducing Octopress Exporter
I've never heard of octopress, interesting. The only thing I don't like is how comments are handled. Since it's all static you relying on an external service like Disqus. I'm not so fond of losing control over user contribution like that. Besides, the actual service (disqus) is pretty terrible anyway. I'm always pissed when the comment I sent gets processed in weird ways yet doesn't do verbatim/code blocks. On Thu, Aug 2, 2012 at 1:21 AM, Tom Alexander wrote: > The important changes are all at the bottom of the file. Basically I > just grab the text before the html preprocessor gets to it and go > through line-by-line to find the code blocks. Have you tried Nicolas Goaziou new parser? org-element.el is a big improvement for org-mode IMHO.
Re: [O] Comments and control lines (# vs. #+)
Hi Samuel, Samuel Wales writes: > Hope it's of some use. Yes it has been. If you pull from latest repo, the way comments are handled have been updated. Specifically, there is no "#+ " anymore. Please check carefully and let us know. -- Bastien
[O] Problem with commented LaTeX header lines
Hi all,
I started to get problems with commented latex headers. All headers
after the commented line seem to be ignored. Is this intended / am I
using the comments wrongly?
Test with new exporter - no cmbright:
,
| #+TITLE: Commented LaTeX headers
|
|
| * Try to export this subtree
| With some text.
|
| And a second paragraph.
|
|
| ** And a section
| With some text.
|
| * Options:noexport:
| ** LaTeX Options
| #+LATEX_HEADER: \usepackage{hyperref}
| # #+LATEX_HEADER: \usepackage{tikz}
| #+LATEX_HEADER: \usepackage{cmbright}
`
Regards,
Andreas
Re: [O] capture template question
On Thu, Aug 02 2012, Tassilo Horn wrote:
> Eric Abrahamsen writes:
>
> Hi Eric,
>
>> I have a capture template that I use for noting gnus messages I want
>> to respond to. What I'd like to end up with is:
>>
>> * EMAIL Respond to [[gnus.mail:sdfdfdfsdfdsfsdf][Bob Johnson]]
>>
>> Where the link address is the message under point, and the link
>> description is the message's %:fromname.
>>
>> I may be dense, but I don't quite see if/how this is possible…
>
> An org-capture-templates entry like that should do:
>
> ("e" "EMAIL" entry
>(file "/home/horn/Repos/org/remember.org") ;; adapt to your needs
>"* EMAIL Respond to %a%?")
>
> In contrast to what you requested, the link's name is something like
>
> Email from Eric Abrahamsen: capture template question
>
> I think, that's even better. (Honestly, it seems there's no gnus link
> support for picking out only the from-part.) :-)
That's what I had before! I hate the big long citation (I seem to get
emails with epic Subject headers), and was trying to make something more
concise.
Rather than trying to add various ways of citing links, perhaps it would
be nice to have a format code for the literal link to the thing under
point at time of capture? What I mean is, something like "%l" so I could
do this:
* EMAIL Respond to [[%l][%:fromname]]%?
Seems like that would add quite a bit of flexibility…
E
--
GNU Emacs 24.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.24.11)
of 2012-08-02 on pellet
7.8.11
[O] org-mode : add note/flag a capture
Is it correct that you cant add a note or change a status to a newly captured item before its been synced into emacs and repulled/synced? I cant see how from the iPhone UI. (I guess I could manually type the note property format in the capture but that would be painful)
Re: [O] capture template question
Eric Abrahamsen writes:
Hi Eric,
> I have a capture template that I use for noting gnus messages I want
> to respond to. What I'd like to end up with is:
>
> * EMAIL Respond to [[gnus.mail:sdfdfdfsdfdsfsdf][Bob Johnson]]
>
> Where the link address is the message under point, and the link
> description is the message's %:fromname.
>
> I may be dense, but I don't quite see if/how this is possible…
An org-capture-templates entry like that should do:
("e" "EMAIL" entry
(file "/home/horn/Repos/org/remember.org") ;; adapt to your needs
"* EMAIL Respond to %a%?")
In contrast to what you requested, the link's name is something like
Email from Eric Abrahamsen: capture template question
I think, that's even better. (Honestly, it seems there's no gnus link
support for picking out only the from-part.) :-)
Bye,
Tassilo
