2011/4/25 Sébastien Vauban :
> Hi John,
>
> John Hendy wrote:
>> Sebastien: my other questions re. how to interpret the code and
>> inserting proper linebreaks are still of interest!
>
> Sorry, just came back today after a 2-week holiday.
>
> Given the number of posts I have to read, could you tell
Hi John,
John Hendy wrote:
> Sebastien: my other questions re. how to interpret the code and
> inserting proper linebreaks are still of interest!
Sorry, just came back today after a 2-week holiday.
Given the number of posts I have to read, could you tell me if all your
questions have been answer
Rasmus writes:
>> It is cool but doesn't play well with margins, as you have seen. I've
>> given up on cool and use the following instead:
>
> I agree on the cool not being cool. However, I do wonder why you would
> want to use /ordinary/ footnotes rather than something easily removable
> such a
> It is cool but doesn't play well with margins, as you have seen. I've
> given up on cool and use the following instead:
I agree on the cool not being cool. However, I do wonder why you would
want to use /ordinary/ footnotes rather than something easily removable
such as fixmenotes, e.g. \fxnot
Hello,
John Hendy writes:
> ,---
> | (latex "\\todo[inline]{\\textbf{\\textsf{%s %s}}\\linebreak{} %s}"
> |'((unless (eq todo "")
> |(format "\\textsc{%s%s}" todo priority))
> | heading content))
> `---
>
> A couple questions:
> - would you be
On Tue, Apr 12, 2011 at 1:20 PM, Eric S Fraga wrote:
> John Hendy writes:
>
> [...]
>
>> - I looked at the package and example and rather liked the side-page
>> type for small little notes. So cool. But, alas, removing the
>> '[inline]' gave me undefined control sequence errors. When I ran it
John Hendy writes:
[...]
> - I looked at the package and example and rather liked the side-page
> type for small little notes. So cool. But, alas, removing the
> '[inline]' gave me undefined control sequence errors. When I ran it
> from the .tex file directly, it kind of worked, but my littl
2011/4/12 John Hendy :
> 2011/4/12 John Hendy :
>>>
>>> Yes, you're right. You need the todonotes package. This is "standard" in my
>>> private class, reason why I forgot about this link.
>>>
>>> Go and add it, you'll love it!
>>
>> Holy cow. I kind of ignored this as I didn't know what it did, the
2011/4/12 John Hendy :
>>
>> Yes, you're right. You need the todonotes package. This is "standard" in my
>> private class, reason why I forgot about this link.
>>
>> Go and add it, you'll love it!
>
> Holy cow. I kind of ignored this as I didn't know what it did, then
> checked out todonotes and wa
>
> Yes, you're right. You need the todonotes package. This is "standard" in my
> private class, reason why I forgot about this link.
>
> Go and add it, you'll love it!
Holy cow. I kind of ignored this as I didn't know what it did, then
checked out todonotes and was blown away. This is amazing.
,
I like formats like this as well and have been "cheating" to do this
in LaTeX more or less like this:
#+attr_latex: align=l|p{0.95\textwidth}
| \,| The text that I want quoted, which ends up looking good but
needs to be on one insanely long line of an org-mode table|
>
John Hendy writes:
> On Thu, Apr 7, 2011 at 12:33 AM, Eric S Fraga wrote:
>> John Hendy writes:
>>
>
>> [...]
>>
>>>
>>> I like formats like this as well and have been "cheating" to do this
>>> in LaTeX more or less like this:
>>>
>>> #+attr_latex: align=l|p{0.95\textwidth}
>>> | \,| The text t
On Thu, Apr 7, 2011 at 12:33 AM, Eric S Fraga wrote:
> John Hendy writes:
>
> [...]
>
>>
>> I like formats like this as well and have been "cheating" to do this
>> in LaTeX more or less like this:
>>
>> #+attr_latex: align=l|p{0.95\textwidth}
>> | \,| The text that I want quoted, which ends up lo
John Hendy writes:
[...]
>
> I like formats like this as well and have been "cheating" to do this
> in LaTeX more or less like this:
>
> #+attr_latex: align=l|p{0.95\textwidth}
> | \,| The text that I want quoted, which ends up looking good but
> needs to be on one insanely long line of an org-m
On Wed, Apr 6, 2011 at 12:33 PM, John Hendy wrote:
> So... if I were just interested in my notes (say I wanted to just push
> the notes to my blog or share them without all the other text), it
> might get odd to see all of those headlines. Can one export just the
> text and hide the headline text
On 4/6/2011 9:33 AM, John Hendy wrote:
> ...
Inline comments already look pretty good, and I can do something like this:
,-
| *** Notes
| Here's some notes just want to see how this looks. Here's some notes
just want to see
| how this looks.
|
| Here's some notes just want to see
On Wed, Apr 6, 2011 at 1:16 PM, Samuel Wales wrote:
> Hi John,
>
> On 2011-04-06, John Hendy wrote:
>> This sounds very cool. I can't gather from the mailing list thread
>> (which appears to be just you) whether this is implemented or just
>> suggested. Is it possible to actually use this or not?
Hi John,
On 2011-04-06, John Hendy wrote:
> This sounds very cool. I can't gather from the mailing list thread
> (which appears to be just you) whether this is implemented or just
> suggested. Is it possible to actually use this or not?
Others have commented on it. Can't find links for you now.
On Wed, Apr 6, 2011 at 12:27 PM, Samuel Wales wrote:
> Hi John,
>
> They only solve half of the problem.
>
> Unbreakable bidirectional links using ID markers would solve
> the teleport problem. Both ends can be moved anyplace,
> including inside stretches of text. They are a little like
> a gene
Hi John,
They only solve half of the problem.
Unbreakable bidirectional links using ID markers would solve
the teleport problem. Both ends can be moved anyplace,
including inside stretches of text. They are a little like
a generalization of footnotes. They use org IDs. You can
specify various
On Wed, Apr 6, 2011 at 11:33 AM, John Hendy wrote:
> On Tue, Apr 5, 2011 at 10:21 PM, Jeff Horn wrote:
>> Have you tried using org-inline-task without a TODO keyword? These
>> super-deep "headlines" aren't treated as headlines, so they don't
>> break doc structure, but they are foldable, and unli
>>
>> Using the following code, you can control whether notes enclosed in
>> "notes" blcks will be exported by changing the value of the
>> *export-my-notes* variable, when it is nil your notes will not be
>> exported, when t they will be exported as quoted text.
>>
>> #+begin_src emacs-lisp
>> (d
On Tue, Apr 5, 2011 at 10:21 PM, Jeff Horn wrote:
> Have you tried using org-inline-task without a TODO keyword? These
> super-deep "headlines" aren't treated as headlines, so they don't
> break doc structure, but they are foldable, and unlike COMMENT keyword
> headlines, they're printable. The on
On Wed, Apr 6, 2011 at 12:02 AM, Eric Schulte wrote:
> Erik Iverson writes:
>
>> If you export to HTML, you should be able to export your notes with a
>> CSS class to style your notes as differently from the text as you
>> like.
>>
>
> I like the following for offsetting quotes, may work well for
On Tue, Apr 5, 2011 at 11:10 PM, Erik Iverson wrote:
> If you export to HTML, you should be able to export your notes with a CSS
> class to style your notes as differently from the text as you like.
Great idea. Unfortunately, I'm almost entirely a LaTeX -> PDF guy.
Though, if I ever wanted blog i
2011/4/5 Eric Schulte :
> Hi John,
>
> Interesting use case, I definitely see the utility. I think that blocks
> may be an appropriate solution, for example if you enclose your notes in
> "notes" blocks, then it should be easy to control whether or not they
> are exported...
Definitely a candidat
Erik Iverson writes:
> If you export to HTML, you should be able to export your notes with a
> CSS class to style your notes as differently from the text as you
> like.
>
I like the following for offsetting quotes, may work well for notes...
#+begin_src css
blockquote {
border-left: 1px s
If you export to HTML, you should be able to export your notes with a CSS class
to style your notes as differently from the text as you like.
On 04/05/2011 10:32 PM, Eric Schulte wrote:
Hi John,
Interesting use case, I definitely see the utility. I think that blocks
may be an appropriate solu
Hi John,
Interesting use case, I definitely see the utility. I think that blocks
may be an appropriate solution, for example if you enclose your notes in
"notes" blocks, then it should be easy to control whether or not they
are exported...
Using the following code, you can control whether notes
Have you tried using org-inline-task without a TODO keyword? These
super-deep "headlines" aren't treated as headlines, so they don't
break doc structure, but they are foldable, and unlike COMMENT keyword
headlines, they're printable. The only problem I've run into is have a
lot to say in an inline
Hi,
One thing I really like to use orgmode for is research. Lately,
there's a mass of stuff on-line that I've been reading though and am
about to start reading through a series of articles and had the idea
to yank them into org for "inline notes."
My current experiment has been:
- wget the websi
31 matches
Mail list logo
