Re: [Orgmode] Lock CLOSED tag
Hello, I didn't know that I could log things like that. Thanks for that hint! Unfortunately, I would prefer to have only one entry and be sure that it wont be overwrited by mistake. Alan On July 10, 2009 01:36:45 pm Nicolas Goaziou wrote: > Alan Boudreault writes: > > > Hello, > > It's maybe not what you're looking for, but you can leave org-log-done > to nil and simply define org-todo-keywords with something like : > > (setq org-todo-keywords '(sequence "TODO(t)" "|" "FIXED(f!)")) > > Nothing should be overwritten then. > > HTH, -- Alan Boudreault Mapgears http://www.mapgears.com ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Newbie Questions
At Fri, 10 Jul 2009 19:48:20 +0200, Nicolas Goaziou wrote: > [...] > Then again, as someone said, a DEADLINE with an appropriate warning > delay would be fine in that case too. I have tasks that have deadlines months in the future and which need tackling from now until the deadline, although obviously not continuously. Putting a warning on the deadline to cover the full time range would fill my agenda view with deadlines, making it rather ineffective! ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Newbie Questions
At Fri, 10 Jul 2009 12:32:59 -0400, Nick Dokos wrote: > Quite likely it's a failure of imagination on my part, but I still > don't see why you would both schedule and deadline an item. Could > you provide a scenario where that would be useful? Well, to use an example that I think the OP (Andrew) would identify with, when a funding agency puts out a call for proposals, they will give a strict deadline (e.g. 12 noon, 5 August 2009). That date is critical to the activity of writing the proposal if one intends to apply for funding so the date gets put in my org file immediately. Subsequently, when I figure out when I will have time to work on writing the proposal, I will schedule the appropriate event. I must admit, however, that I do frequently simply put an active time stamp on the note for when I want to work on this task. I guess it depends on the "granularity" of the scheduling of the task: if I intend to work on it at some specific hour of the day, I'll use a time stamp; if I intend to tackle the task "sometime" on Thursday, I'll schedule it. The latter may be the wrong way to do it but the reality is that my "planned" schedule often goes completely out the window due to external factors and any time stamped activities disappear off the agenda view the following day whereas scheduled items do not. This makes scheduling appealing as it allows me to say, the next day, "ooops, I forgot to actually work on that proposal yesterday...". YMMV, of course! cheers, eric ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Newbie Questions
Nick Dokos writes: > Quite likely it's a failure of imagination on my part, but I still > don't see why you would both schedule and deadline an item. Could > you provide a scenario where that would be useful? I think the OP has a time frame to execute some task. He doesn't want to be bugged about it before SCHEDULED, and it will be too late after DEADLINE. Imagine you have to make a gift to someone on Sunday, but got so much work to do that you won't be able to go to the mall before Thursday... oh well, you can always buy online then, but that would defeat the point of my example. Then again, as someone said, a DEADLINE with an appropriate warning delay would be fine in that case too. -- Nicolas Goaziou ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Newbie Questions
"Andrew M. Nuxoll" writes: > 1. When I view my agenda for a day it displays TODO items twice if they > are both SCHEDULED and DEADLINEd (a common occurrence for me). Can this > be avoided? Here's a generic example snippet from my agenda: >Thursday9 July 2009 > nux:Scheduled: TODO [#B] Call Mary :PROJECT:: > nux:In 1 d.: TODO [#B] Call Mary :PROJECT:: I think this is a feature. For example, if I get some books from a library, I use the deadline to mark when I absolutely must return the books. The schedule tells me: Hey, I am near the library this day, so I *want* to do this today. I absolutely want both informations in my agenda. >From the manual: DEADLINE Meaning: the task (most likely a TODO item, though not necessarily) is supposed to be finished on that date. SCHEDULED Meaning: you are planning to start working on that task on the given date. You can set a different deadline for each item, but "avoiding this" totally means avoiding crucial information in your agenda. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Lock CLOSED tag
Alan Boudreault writes: Hello, It's maybe not what you're looking for, but you can leave org-log-done to nil and simply define org-todo-keywords with something like : (setq org-todo-keywords '(sequence "TODO(t)" "|" "FIXED(f!)")) Nothing should be overwritten then. HTH, -- Nicolas Goaziou ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Newbie Questions
Eric S Fraga wrote: > At Thu, 09 Jul 2009 21:08:31 -0700, > Andrew M. Nuxoll wrote: > > In my mind, there is no conflict between scheduling and deadlining. > > I agree with you on this point but, in this case, it makes sense for > both aspects to be highlighted in the agenda view. I would suggest > that you might wish to change (reduce) the warning period for the > deadline when you schedule an item or alternatively not schedule an > item but simply assign an appointment date/time (i.e. an active time > stamp) to it for when you want to work on the task. The latter is > what I do in many cases. > Quite likely it's a failure of imagination on my part, but I still don't see why you would both schedule and deadline an item. Could you provide a scenario where that would be useful? Thanks, Nick ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Newbie Questions
At Thu, 09 Jul 2009 21:08:31 -0700, Andrew M. Nuxoll wrote: > In my mind, there is no conflict between scheduling and deadlining. I agree with you on this point but, in this case, it makes sense for both aspects to be highlighted in the agenda view. I would suggest that you might wish to change (reduce) the warning period for the deadline when you schedule an item or alternatively not schedule an item but simply assign an appointment date/time (i.e. an active time stamp) to it for when you want to work on the task. The latter is what I do in many cases. eric ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] further on compiling development version of org-mode without make command
Stefan Vollmar writes: > Dear Sebastian, > > On 09.07.2009, at 20:25, Sebastian Rose wrote: > >> this works here with `emacs -Q' >> >> we forgot the load path >> The function is likely to change some more. I just send this version, so >> you can compile this way (hopefully). > > > EXCELLENT - we now have an up-to-date org-mode even for Emacs on MS Windows, > it > worked beautifully - thank you! > > A newer version of Sebastian's script is available here: > http://orgmode.org/worg/org-hacks.php#compiling-org-without-make Good to here, that it worked on Windows (I always have to start my VM to test there, and Win32 emacs is not that good configured here yet...). Just pushed a version, that needs no dired and kills the `install.el'. So all that remains is the `*Compile-Log*' buffer, which might be of some use. I find that less annoying. Also, the autoload file is loaded after compiling. Sebastian ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] further on compiling development version of org-mode without make command
Dear Sebastian, On 09.07.2009, at 20:25, Sebastian Rose wrote: this works here with `emacs -Q' we forgot the load path The function is likely to change some more. I just send this version, so you can compile this way (hopefully). EXCELLENT - we now have an up-to-date org-mode even for Emacs on MS Windows, it worked beautifully - thank you! A newer version of Sebastian's script is available here: http://orgmode.org/worg/org-hacks.php#compiling-org-without-make Warm regards, Stefan -- Dr. Stefan Vollmar, Dipl.-Phys. Max-Planck-Institut für neurologische Forschung Gleuelerstr. 50, 50931 Köln, Germany Tel.: +49-221-4726-213 FAX +49-221-4726-298 Tel.: +49-221-478-5713 Mobile: 0160-93874279 Email: voll...@nf.mpg.de http://www.nf.mpg.de ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: AW: Bug in LaTeX export
"Holst Thomas (DS-ET/ECF1)" writes: > > yes I have transient-mark-mode enabled. > > Here is a simpler example to reproduce the bug: > --8<---cut here---start->8--- > * Kapitel 1 >dingens >foo bar > * Kapitel 2 > bar foo > --8<---cut here---end-->8--- > > If you try to export only subtree 'Kapitel 1' to LaTeX you also have > 'Kapitel 2' in the LaTeX output. With this example, I can reproduce the bug. Best, Matt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Lock CLOSED tag
Hi, Is it possible to lock the CLOSED tag ? It may happen that I set back a FIXED tag to TODO by mistake, The problem is that when I re-set it to FIXED, the closed tag is overwrited. I would like to lock the closed tag as soon as it is set to a done tag. Best regards, Alan -- Alan Boudreault Mapgears http://www.mapgears.com ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Latest Org and Carbon Emacs
Peter Frings writes: > On 09 Jul 2009, at 23:32, Matthew Lundin wrote: > >> I found it easiest to install the new org files directly to the >> Emacs.app directory. > > I've seen this approach mentioned several times, but I think it makes > things more complicated then they should be. By keeping the app and > the libs in separate places, the two can be updated independently. > Emacs provides ample ways of supporting this style -- actually, I > guess it was meant to work that way, until the bundles came along... Exactly. The beauty of Emacs is that there are multiple options for everything. Overwriting org when I updated Carbon Emacs wasn't really an issue for me because 1) Carbon Emacs is very rarely updated 2) I pull the latest changes from the git repo and run make && make install every day. The reason I just threw org-mode in the Emacs.app directory is that I also had EmacsCVS.app and wanted to keep separate byte-compiled for Emacs 22 and Emacs 23. If you're looking for the simplest way to install a byte-compiled org-mode, I believe you could just clone the git repository to ~/org-mode, run make in the directory, and then add ~/org-mode/lisp to your load path. > Of course, it's very convenient when you download Carbon Emacs (or > others) that everything is in place, but since when do Linuxers care > about convenience? :-) Well, I suppose in this case convenience is in the eye of the beholder. E.g., pacman -S emacs-cvs. ;) Best, Matt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] AW: Bug in LaTeX export
Hello Matt, > Von: Matthew Lundin [mailto:m...@imapmail.org] > Betreff: Re: Bug in LaTeX export > > "Holst Thomas (DS-ET/ECF1)" writes: >> [Problem exporting a subtree with no further subsubtrees] > Do you have transient-mark-mode enabled? I tested this with Emacs 22 > and when transient-mark-mode was enabled, it exported correctly (i.e., > just the 1st tree). When transient-mark-mode was turned off, I got the > results you describe above. > Just a thought... yes I have transient-mark-mode enabled. Here is a simpler example to reproduce the bug: --8<---cut here---start->8--- * Kapitel 1 dingens foo bar * Kapitel 2 bar foo --8<---cut here---end-->8--- If you try to export only subtree 'Kapitel 1' to LaTeX you also have 'Kapitel 2' in the LaTeX output. Thomas ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bug in LaTeX export
"Holst Thomas (DS-ET/ECF1)" writes:
> I think I discoverd a bug in LaTeX export. I mark a subtree with C-c @
> and then export it to LaTeX with C-c C-e L.
>
> If the subtree has no further subtrees the LaTeX-file not only contains
> the region, but also the rest of the document to the end.
>
> Here is an example:
>
> ,[ test.org ]
> | * Kapitel 1
> | ** Kapitel 1.1
> |foo bar
> | * Kapitel 2
> | bar foo
> `
>
> If the Kapitel 1.1 subtree is marked the LaTeX output looks like this:
>
> ,[ LaTeX output ]
> | % Created 2009-07-10 Fr 12:33
> | \documentclass[11pt,a4paper]{article}
> | \usepackage[latin1]{inputenc}
> | \usepackage[T1]{fontenc}
> | \usepackage{hyperref}
> |
> |
> | \title{Kapitel 1.1}
> | \author{Holst Thomas}
> | \date{10 Juli 2009}
> |
> | \begin{document}
> |
> | \textbf{Kapitel 1.1}
> |
> | \setcounter{tocdepth}{3}
> | \tableofcontents
> | \vspace*{1cm}
> |foo bar
> | \begin{itemize}
> | \item Kapitel 2
> | bar foo
> | \end{itemize}
> |
> | \end{document}
> `
>
> Kapitel 2 is also included. This does not happen if the subtree has
> additonal subtrees. If I mark the Kapitel 1 subtree the output is as
> expected.
>
> When the bug happens, `org-export-latex-default-class' does not work.
> Instead the class 'article' is used.
>
> It does not happen if the region is exported to ASCII or HTML.
>
> My setup is:
>
> emacs 22.2.1, WinXP, org-mode 6.28trans from yesterday.
Do you have transient-mark-mode enabled? I tested this with Emacs 22 and
when transient-mark-mode was enabled, it exported correctly (i.e., just
the 1st tree). When transient-mark-mode was turned off, I got the
results you describe above.
Just a thought...
Best,
Matt
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Error when exporting as Latex
Karl Maihofer writes: > Others may correct me but I think this is the same issue I had yesterday. The > reason is that the two versions of Org - the one shipped with your Emacs and > the > latest one you installed by yourself conflict in some way. Some time ago the > lisp-file for LaTeX export was renamed - > perhaps this is why you get an error. My solution was to rename the > Org-lisp-files in c:/bin/emacs-22.3/lisp/textmodes/. For example > org-export-latex.elc gets org-export-latex.elc_save and so on. After that > Emacs > can only find the latest Org-version. > > I then had to add > > (require 'org-latex) I think adding the git-Org's lisp directory to the load path (add-to-list 'load-path "~/path/to/org/lisp/") should suffice, provided the lisp files are compiled. In that case a second line should do: (require 'org-install) But I'm not sure this works. I simply do sh$ rm -rf /usr/local/share/emacs/23.50.XX/lisp/org after upgrading emacs, hence I cannot test it now. This aspect of the load-path mechanism is not very well documented. Sebastian ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bug in LaTeX export
"Holst Thomas (DS-ET/ECF1)" writes:
> Hello,
>
> I think I discoverd a bug in LaTeX export. I mark a subtree with C-c @
> and then export it to LaTeX with C-c C-e L.
>
> If the subtree has no further subtrees the LaTeX-file not only contains
> the region, but also the rest of the document to the end.
>
> Here is an example:
>
> ,[ test.org ]
> | * Kapitel 1
> | ** Kapitel 1.1
> |foo bar
> | * Kapitel 2
> | bar foo
> `
>
> If the Kapitel 1.1 subtree is marked the LaTeX output looks like this:
>
> ,[ LaTeX output ]
> | % Created 2009-07-10 Fr 12:33
> | \documentclass[11pt,a4paper]{article}
> | \usepackage[latin1]{inputenc}
> | \usepackage[T1]{fontenc}
> | \usepackage{hyperref}
> |
> |
> | \title{Kapitel 1.1}
> | \author{Holst Thomas}
> | \date{10 Juli 2009}
> |
> | \begin{document}
> |
> | \textbf{Kapitel 1.1}
> |
> | \setcounter{tocdepth}{3}
> | \tableofcontents
> | \vspace*{1cm}
> |foo bar
> | \begin{itemize}
> | \item Kapitel 2
> | bar foo
> | \end{itemize}
> |
> | \end{document}
> `
I can't reproduce this. Here is the output when I type C-c @ and C-c C-e
L. (I just pulled the most recent org from the git repo for emacs 22):
--8<---cut here---start->8---
% Created 2009-07-10 Fri 07:10
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{hyperref}
\title{Kapitel 1}
\author{Matthew Lundin}
\date{10 July 2009}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
\section{Kapitel 1.1}
\label{sec-1}
foo bar
\end{document}
--8<---cut here---end--->8---
What are your other org-latex settings?
Best,
Matt
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Error when exporting as Latex
Karl Maihofer writes: > Others may correct me but I think this is the same issue I had yesterday. The > reason is that the two versions of Org - the one shipped with your Emacs and > the > latest one you installed by yourself conflict in some way. Some time ago the > lisp-file for LaTeX export was renamed - > perhaps this is why you get an error. My solution was to rename the > Org-lisp-files in c:/bin/emacs-22.3/lisp/textmodes/. For example > org-export-latex.elc gets org-export-latex.elc_save and so on. After that > Emacs > can only find the latest Org-version. > > I then had to add > > (require 'org-latex) > > to my ~/.emacs. Hope that helps. > Karl Karl that worked, thanks! It does beg the question of why these files aren't overwritten during the installation from the git repo - I do the usual make clean && make install && make doc routine. Is there something that I should be amending before I do this? Paul ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Bug in LaTeX export
Hello,
I think I discoverd a bug in LaTeX export. I mark a subtree with C-c @
and then export it to LaTeX with C-c C-e L.
If the subtree has no further subtrees the LaTeX-file not only contains
the region, but also the rest of the document to the end.
Here is an example:
,[ test.org ]
| * Kapitel 1
| ** Kapitel 1.1
|foo bar
| * Kapitel 2
| bar foo
`
If the Kapitel 1.1 subtree is marked the LaTeX output looks like this:
,[ LaTeX output ]
| % Created 2009-07-10 Fr 12:33
| \documentclass[11pt,a4paper]{article}
| \usepackage[latin1]{inputenc}
| \usepackage[T1]{fontenc}
| \usepackage{hyperref}
|
|
| \title{Kapitel 1.1}
| \author{Holst Thomas}
| \date{10 Juli 2009}
|
| \begin{document}
|
| \textbf{Kapitel 1.1}
|
| \setcounter{tocdepth}{3}
| \tableofcontents
| \vspace*{1cm}
|foo bar
| \begin{itemize}
| \item Kapitel 2
| bar foo
| \end{itemize}
|
| \end{document}
`
Kapitel 2 is also included. This does not happen if the subtree has
additonal subtrees. If I mark the Kapitel 1 subtree the output is as
expected.
When the bug happens, `org-export-latex-default-class' does not work.
Instead the class 'article' is used.
It does not happen if the region is exported to ASCII or HTML.
My setup is:
emacs 22.2.1, WinXP, org-mode 6.28trans from yesterday.
I also observed this bug with org-mode 6.28b. And when I start emacs
with the option '-Q'.
Thomas
--
"Das Leben ist so einfach,
dass es schon wieder schwierig ist!"
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Error when exporting as Latex
Others may correct me but I think this is the same issue I had
yesterday. The reason is that the two versions of Org - the one shipped
with your Emacs and the latest one you installed by yourself conflict in
some way. Some time ago the lisp-file for LaTeX export was renamed -
perhaps this is why you get an error. My solution was to rename the
Org-lisp-files in c:/bin/emacs-22.3/lisp/textmodes/. For example
org-export-latex.elc gets org-export-latex.elc_save and so on. After
that Emacs can only find the latest Org-version.
I then had to add
(require 'org-latex)
to my ~/.emacs. Hope that helps.
Karl
Paul Mead schrieb:
Hi
I've only just spotted this error as I don't use the Latex export very
often. When I export as Latex either to file or buffer, I get the
following error:
org-export-latex-lists: Wrong number of arguments: #[(list)
"\"" [list org-list-to-generic (:splicep nil :ostart
"\\begin{enumerate}" :oend "\\end{enumerate}" :ustart "\\begin{itemize}"
:uend "\\end{itemize}" ...)] 3
("c:/bin/emacs-22.3/lisp/textmodes/org-export-latex.elc" . 39820)], 2
I've tested this on a file which is unchanged from when I last
successfully exported it, many org versions ago.
Org-mode version 6.28trans
GNU Emacs 22.3.1 (i386-mingw-nt5.1.2600) of 2008-09-06 on SOFT-MJASON
Any ideas?
Thanks, Paul
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Error when exporting as Latex
Hi
I've only just spotted this error as I don't use the Latex export very
often. When I export as Latex either to file or buffer, I get the
following error:
org-export-latex-lists: Wrong number of arguments: #[(list)
"\"" [list org-list-to-generic (:splicep nil :ostart
"\\begin{enumerate}" :oend "\\end{enumerate}" :ustart "\\begin{itemize}"
:uend "\\end{itemize}" ...)] 3
("c:/bin/emacs-22.3/lisp/textmodes/org-export-latex.elc" . 39820)], 2
I've tested this on a file which is unchanged from when I last
successfully exported it, many org versions ago.
Org-mode version 6.28trans
GNU Emacs 22.3.1 (i386-mingw-nt5.1.2600) of 2008-09-06 on SOFT-MJASON
Any ideas?
Thanks, Paul
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Markup for export question
Hi Giovanni,
Giovanni Ridolfi wrote:
> --- Gio 9/7/09, Ulf Stegemann ha scritto:
>> When writing documentations I often
>> come across expressions like
>>
>> doMagic('myVariable')
>>
>> In an ideal world the HTML code for this after exporting the org file
>> would look like this:
>>
>> doMagic('myVariable')
>>
>> The purpose is of course to indicate that `doMagic' is a literal
>> function/method name while `myVariable' is not meant literal and is
>> to be replaced something more or less sensible.
>
> ... did you play with "Literal examples", chapter 12.1 of the manual?
>
> or "12.6.6 Text areas" ?
yes, I'm aware of those but I was rather referring to inline markup not
src/example blocks. To make it clearer, imagine something like this:
Copy your configuration to /install-dir/conf.
Which ideally would be exported as
Copy your configuration to /install-dir/conf.
This is something where a src/example block is not suitable.
Ulf
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Latest Org and Carbon Emacs
On 09 Jul 2009, at 23:32, Matthew Lundin wrote: Karl Maihofer writes: Until now I used Org with Debian GNU/Linux. Today I bought a MacBook Pro 13" and I spent the evening making my first steps with MacOS. I installed the Carbon Emacs package and configured Emacs to use the latest Org-Version that I copied to ~/elisp/org-mode/. If I remember correctly. the old org lisp files are located in /Applications/Emacs.app/Contents/Resources/lisp/textmodes. I found it easiest to install the new org files directly to the Emacs.app directory. I've seen this approach mentioned several times, but I think it makes things more complicated then they should be. By keeping the app and the libs in separate places, the two can be updated independently. Emacs provides ample ways of supporting this style -- actually, I guess it was meant to work that way, until the bundles came along... Of course, it's very convenient when you download Carbon Emacs (or others) that everything is in place, but since when do Linuxers care about convenience? :-) Cheers, Peter. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Newbie Questions
Andrew M. Nuxoll wrote: Nick Dokos wrote: Just an FYI (a nice one since Carsten said so :-): Carsten is the first name, Dominik (no c) is the surname of the creator of Org-mode. And I promise we'll be nice even after he comes back :-) Err, whoops! So let me turn the question around: why do you need to both SCHEDULE and DEADLINE the same item? In my mind, there is no conflict between scheduling and deadlining. So, I may be missing something. In my case, I am scheduling myself to work on an item that has a deadline. I don't think that's an unusual scenario. For example, I have a grant proposal I need to have a draft of by Monday (DEADLINE) but I've scheduled Thursday afternoon to work on it. By putting SCHEDULED on it means that it gets attention on that day unless Murphy steps in. If Murphy does, then I still have the benefit of the DEADLINE to keep me apprised of my dire situation. An alternative (which I don't like) is to not use DEADLINE on a SCHEDULED item. Instead, I can just attach a second date to the item and label it "deadline" or "drop dead date." So, the best option I have now is to ignore the double entry. I was hoping there was a magic variable(TM) for this like there was with the other issue. You could specify a per deadline warning period. The example for the manual: DEADLINE: <2004-02-29 Sun -5d>, which will start prompting you 5 days before the deadline. I use this to remind me that I need to start working on something which has a fixed deadline. Ian. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
