Re: [O] Emphasis in title export
I played around with it for a little bit and now the export is working fine. I'm not sure exactly what I changed, but it's working as intended now. Thanks, Will On Mon, Apr 28, 2014 at 6:10 PM, Leonard Randall < leonard.a.rand...@gmail.com> wrote: > Hi Will, > > The example works fine for me. It seems like the most likely cause of your > issue is your export settings. One thing that you might try is to add this > to the top of your file. > > #+Options: *:t > > If you already have an options section on your file you may want to check > that you do not have *:nil anywhere in this line. If you do change it to > `*:t as in the example above. You might also want to check that you have > not set `org-export-with-emphasis' to nil anywhere in your init file. > > More info on configuring export settings can be found here: > http://orgmode.org/manual/Export-settings.html > > Hope this helps! > > All best, > Leonard > > > On 28 April 2014 15:17, William Kunkel wrote: > >> I have a title in which I need to have some text in italics. I tried this: >> >> #+TITLE: Analysis of Sartre's /No Exit/ >> >> But the slashes were just exported literally, instead of italicizing. >> This seemed like a pretty basic problem, but I've been unable to find >> anything about it via Google or in the list archives. Is there a simple >> solution? >> >> Thanks, >> Will >> > >
[O] Emphasis in title export
I have a title in which I need to have some text in italics. I tried this: #+TITLE: Analysis of Sartre's /No Exit/ But the slashes were just exported literally, instead of italicizing. This seemed like a pretty basic problem, but I've been unable to find anything about it via Google or in the list archives. Is there a simple solution? Thanks, Will
[O] Org-Babel concise named scalar variables
I'm just getting started using Org Babel and I've run into a bit of an annoyance that I can't seem to find an answer to in the Org Babel docs. I find myself wanting to use one variable in multiple code blocks, for example, the path to a file. Org Babel provides several mechanisms for including array/list types, via tables and lists with a #+NAME line before them. However the only mechanism it provides for single variables is #+NAME before example blocks, which just seem clunky for something as trivial as a file path or numeric variable. Is there a more concise way to do simple variables, or am I stuck with the named example blocks? Thanks, Will
Re: [O] Recording results of TODO items
Alright, I'll just do my own thing then, I suppose. Thanks! On Tue, Apr 15, 2014 at 10:48 PM, Eric Abrahamsen wrote: > William Kunkel writes: > > > I could well add it in a sub-heading under the TODO, I was just > > curious if there was a built-in org-mode way that I ought to be using > > instead of rolling something of my own. > > Ah, no -- I think the state-change note is about as built-in as it gets... > > > Cheers, > > Will > > > > > > On Tue, Apr 15, 2014 at 10:27 PM, Eric Abrahamsen < > > e...@ericabrahamsen.net> wrote: > > > > William Kunkel writes: > > > > > Is there a standard way to record the outcomes of certain TODO > > items? > > > For example, I had a TODO item to research and come to a > > decision > > > about part of the architecture of a software project I'm > > starting, > > > and I'd like to record the result of that TODO item, that is, > > the > > > decision that I made. I found "closing notes" for TODO items, > > but > > > that's an option that applies to all TODO items and seems more > > > intended for brief remarks (to me, at least). Is using the > > closing > > > notes functionality my best bet, or is there something better? > > > > > > Thanks, > > > Will > > > > I do usually use the logging/notes functionality, but if you need > > more > > text, why not just make it the body of the TODO? A TODO is a > > heading > > like any other, you can just put a description of the outcome > > underneath > > it. If that gets unwieldy, separate the bits into multiple > > sub-headings, > > and/or make the TODO itself one smaller part of a larger TODO. > > > > > > >
Re: [O] Recording results of TODO items
I could well add it in a sub-heading under the TODO, I was just curious if there was a built-in org-mode way that I ought to be using instead of rolling something of my own. Cheers, Will On Tue, Apr 15, 2014 at 10:27 PM, Eric Abrahamsen wrote: > William Kunkel writes: > > > Is there a standard way to record the outcomes of certain TODO items? > > For example, I had a TODO item to research and come to a decision > > about part of the architecture of a software project I'm starting, > > and I'd like to record the result of that TODO item, that is, the > > decision that I made. I found "closing notes" for TODO items, but > > that's an option that applies to all TODO items and seems more > > intended for brief remarks (to me, at least). Is using the closing > > notes functionality my best bet, or is there something better? > > > > Thanks, > > Will > > I do usually use the logging/notes functionality, but if you need more > text, why not just make it the body of the TODO? A TODO is a heading > like any other, you can just put a description of the outcome underneath > it. If that gets unwieldy, separate the bits into multiple sub-headings, > and/or make the TODO itself one smaller part of a larger TODO. > > >
[O] Recording results of TODO items
Is there a standard way to record the outcomes of certain TODO items? For example, I had a TODO item to research and come to a decision about part of the architecture of a software project I'm starting, and I'd like to record the result of that TODO item, that is, the decision that I made. I found "closing notes" for TODO items, but that's an option that applies to all TODO items and seems more intended for brief remarks (to me, at least). Is using the closing notes functionality my best bet, or is there something better? Thanks, Will
Re: [O] Navigating description lists
Haha, that's a lot more clever than what I was trying to do. Thanks for pointing that out. - Will On Mon, Apr 7, 2014 at 11:20 AM, Nicolas Goaziou wrote: > Hello, > > William Kunkel writes: > > > I use description lists a lot in org documents, and I find myself > following > > a certain pattern to add new ones: > > > >1. Put the cursor on another item and hit M- to create a new item > >2. Enter the first part of the list item > >3. Hit , , , > >4. Enter the second part of the list item > > > > Frequently, I find myself hitting to try to do step 3, which > indents > > the line, which I then have to undo. Is there a key combination which > does > > step 3 without needing to hit four keys sequentially? > > C-e > > > Regards, > > -- > Nicolas Goaziou >
[O] Navigating description lists
I use description lists a lot in org documents, and I find myself following a certain pattern to add new ones: 1. Put the cursor on another item and hit M- to create a new item 2. Enter the first part of the list item 3. Hit , , , 4. Enter the second part of the list item Frequently, I find myself hitting to try to do step 3, which indents the line, which I then have to undo. Is there a key combination which does step 3 without needing to hit four keys sequentially? Thanks, Will
Re: [O] Compiling Org Mode on Windows - "date" Bug?
Wow, I sure feel silly now. This is so much easier than trying to get the damn thing compiled under Windows. Thanks! - Will On Sun, Apr 6, 2014 at 2:23 PM, Achim Gratz wrote: > William Kunkel writes: > > Does the ELPA package include packages not bundled with Emacs (Those > > marked "C" in customize-variable org-modules)? > > The org-plus-contrib package does. > > > Regards, > Achim. > -- > +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ > > SD adaptation for Waldorf microQ V2.22R2: > http://Synth.Stromeko.net/Downloads.html#WaldorfSDada > > >
Re: [O] Compiling Org Mode on Windows - "date" Bug?
Does the ELPA package include packages not bundled with Emacs (Those marked "C" in customize-variable org-modules)? Installing it didn't seem to make the org-drill module available. As for the date problem, I guess it's trying to use cmd as my default shell and generating the temporary batch script automatically; I'll try to get that sorted out somehow. Thanks, Will On Sun, Apr 6, 2014 at 3:02 AM, Achim Gratz wrote: > William Kunkel writes: > > I've traced the problem to the fact that make is trying to run a > > temporary batch script with cmd, with the contents: > > > > @echo off > > date +%Y-%m-%d > > There is no such batch script in the entire Org distribution, nor should > the build system ever try to run cmd for anything (you really need a > POSIX shell for anything make doesn't use built-ins for), so it seems > you're using some strange make and/or have the PATH set incorrectly. If > you're not using a recent GNU Make, you can try to compile Org without > one (as described in the FAQ on Worg), however I'd suggest you use the > ELPA package instead. > > That said, the result of the particular invocation that requires date is > only used in the documentation, so if you really want to see how far you > can progress beyond that, simply remove the "$(shell date +%Y-%m-%d)" in > mk/targets.mk and replace it with the current date like "2014-04-06". > > > Regards, > Achim. > -- > +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ > > SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: > http://Synth.Stromeko.net/Downloads.html#WaldorfSDada > > >
[O] Compiling Org Mode on Windows - "date" Bug?
Hi all, I, for reasons I cannot control, have to use Windows. I've been using emacs and the version of org mode packaged with emacs. However, I've wanted to use org-drill, which as far as I understand requires compiling org-mode from source. I copied local.mk from the "Emacs on Windows" section here: http://orgmode.org/worg/dev/org-build-system.html. However, when I then run make, it hangs. I've traced the problem to the fact that make is trying to run a temporary batch script with cmd, with the contents: @echo off date +%Y-%m-%d As "+%Y-%m-%d" is not valid input to the DOS "date" command, (which, unlike the Linux version, only sets the date), it prompts for acceptable input and the program hangs. Why is this happening, and how can I make it not happen? Thanks, Will Kunkel
