> >
> > #+attr_latex: :environment tabulary :width \textwidth :align L|RR
>
> For the record, for simple ":align" strings, you can also use Org
> syntax:
>
> | / | > | | | | | | |
> | | | | | | | | |
> | | a | b | c | d | e | f | g |
>
>
> how do I filter so that only the items with :RESEARCH: tag are displayed.
Just a quick follow-up to my own post. I realize now that I need to run C-C-c
C-x C-c *after* running C-c a s +{research} -done
Thanks for the help!
On 12 Apr 2013 11:58, "Bastien" wrote:
>
> Hi Samuel,
>
> I'm convinved now, and switching to "state" without any TODO keyword
> will now remove the CLOSED planning information.
>
> Thanks,
>
> --
> Bastien
Hi Bastien and all,
I am afriad you saw this coming:
Could that be an option? I activel
Hi Nicolas,
On Sat, Apr 13, 2013 at 10:42:12PM +0200, Nicolas Goaziou wrote:
> Hello,
>
> Suvayu Ali writes:
>
> > The info manual does not compile because of a wrong next node entry in
> > org.texi. A fix is attached.
>
> Thank you for the patch.
>
> You need to add TINYCHANGE at the end of
Thanks, Bastien!
Column view is very nice.
> The easiest way to achieve this is to have a column view in your Org
> file like this:
>
> #+COLUMNS: %30ITEM %TODO %PRIORITY %15SCHEDULED %15DEADLINE
>
> Then in the agenda, C-c C-x C-c will display the column view.
This allows me to do most of wha
> > Anyhow, this works:
> >
> > #+attr_latex: :environment tabulary :width \textwidth :align L|RR
>
> What was the fix? Using =:environment tabulary= ? Or was it a syntax error?
>
I don't know actually :). I guess I was trying various things, quoting
the strings, using :options, etc. It was
When I attempt to export a .org file to Beamer (with "C-c C-e l b" after
requiring ox-beamer) I get the following error [1]. From the info page
(info "(org)Beamer export") it looks like I shouldn't have to do any
special buffer preparation.
What am I doing wrong?
Thanks,
Footnotes:
[1]
Debug
Hi,
I was quite surprised after pulling down master to find that C-o has
been bound to org-ctrl-o (commit 45d6d8f8 2013-04-05 11:14:20 +0200).
I personally don't use open-line much myself so remap this key for my own use.
Wouldn't it be better to do something like:
(define-key org-mode-map
Hello,
Nicolas Goaziou wrote:
> Bastien writes:
>
>> I would find it both cleaner and more useful for users to extend
>> `org-export-with-timestamps' with three choices:
>>
>> 'inactive-not-standalone
>> 'active-not-standalone
>>'not-standalone
>
> This is a different idea. The
Hi Eric,
Here is old not-working not-finished code that I abandoned. But it
illustrates the goal.
Samuel
===
Maybe something like:
- In source file, C-c ' to go to Org entry associated with nearest ID marker
- C-u C-c ' to create ID marker and create its Org entry in your Org file
Hi Thorsten,
On 4/12/13, Thorsten Jolitz wrote:
> If you structure your Emacs Lisp files the 'outshine way', you can
> convert them into complete Org files fast and easily using 'outorg.el'.
No, we are talking about different things.
With what I am talking about, you can:
- put your Org note
On Sat, Apr 13, 2013 at 01:31:17PM +0800, Eric Abrahamsen wrote:
> Eric Abrahamsen writes:
>
> > François Pinard writes:
> >
> >> Bastien writes:
> >>
> >>> Eric Abrahamsen writes:
> >>
> The first step is probably to research the differences between xhtml and
> html 5.
> >>
> >>> We
Hello,
Suvayu Ali writes:
> The info manual does not compile because of a wrong next node entry in
> org.texi. A fix is attached.
Thank you for the patch.
You need to add TINYCHANGE at the end of the commit message before I can
apply it.
Regards,
--
Nicolas Goaziou
On 4/12/13, Bastien wrote:
> I'm convinved now, and switching to "state" without any TODO keyword
> will now remove the CLOSED planning information.
Thanks, Bastien. One of the great things about Org is its attention
to detail, and that includes little orthogonality pieces.
Samuel
--
The Kafk
hi,
The info manual does not compile because of a wrong next node entry in
org.texi. A fix is attached.
--
Suvayu
Open source is the future. It sets us free.
>From bed20723adc4700df5289804ab4254d705fe148f Mon Sep 17 00:00:00 2001
From: Suvayu Ali
Date: Sat, 13 Apr 2013 21:33:17 +0200
Subject:
Bastien writes:
> I would find it both cleaner and more useful for users to extend
> `org-export-with-timestamps' with three choices:
>
> 'inactive-not-standalone
> 'active-not-standalone
>'not-standalone
This is a different idea. The change would happen at the exporter level,
Bastien writes:
> Hi David,
>
> da...@adboyd.com (J. David Boyd) writes:
>
>> Hmm, then is there any method in Org to auto-download the image, and then
>> inline it?
>
> No.
>
>> Or in other words, do attachments have to be locally available, or will a URL
>> work to attach something?
>
> The for
On Fri, Apr 12, 2013 at 10:06:21AM +0800, Eric Abrahamsen wrote:
> François Pinard writes:
>
> > Christian Moe writes:
> >
> > While on this subject! :-)
> >
> > Could Org allow the output of HTML5 rather than XHTML, under the control
> > of some option? I've read that some frameworks really ex
On Sat, Apr 13, 2013 at 6:50 AM, Vikas Rawal
wrote:
>
>> And I still mean #+attr_ latex: :width :) You're still missing a colon.
>>
>
> :). Sorry, I was not copying and pasting.
>
> Anyhow, this works:
>
> #+attr_latex: :environment tabulary :width \textwidth :align L|RR
What was the fix? Usi
Hello,
Vikas Rawal writes:
> Anyhow, this works:
>
> #+attr_latex: :environment tabulary :width \textwidth :align L|RR
For the record, for simple ":align" strings, you can also use Org
syntax:
| / | > | | | | | | |
| | | | | | | | |
| | a | b |
> Date: Sat, 13 Apr 2013 13:24:13 +0100
> From: "Sean O'Halpin"
> Cc: Carsten Dominik , Org Mode
>
>
> In your opinion, would it be possible to reproduce the functionality
> of outline-mode using text properties rather than overlays?
This needs to be analyzed. Outline mode uses several featur
"Sean O'Halpin" writes:
> In your opinion, would it be possible to reproduce the functionality
> of outline-mode using text properties rather than overlays? And in the
> case of org-mode, would this really make that much of a difference in
> terms of performance?
Broadly speaking, answer seems t
Michael Strey writes:
> Robert,
>
> On Mo, Apr 08, 2013 at 09:44:12 -0500, Robert Goldman wrote:
>> Michael Strey wrote:
>> > Currently org-phone.el as well as my org-dial.el are incompatible with
>> > org-contacts. The only idea behind my proposal was to make the
>> > contributors
>> > of both
Nicolas Goaziou writes:
> Is that OK with you?
I still resist this idea.
I would find it both cleaner and more useful for users to extend
`org-export-with-timestamps' with three choices:
'inactive-not-standalone
'active-not-standalone
'not-standalone
When set to 'not-standalo
In your opinion, would it be possible to reproduce the functionality
of outline-mode using text properties rather than overlays? And in the
case of org-mode, would this really make that much of a difference in
terms of performance?
Regards,
Sean
On Fri, Apr 12, 2013 at 1:36 PM, Eli Zaretskii wro
> And I still mean #+attr_ latex: :width :) You're still missing a colon.
>
:). Sorry, I was not copying and pasting.
Anyhow, this works:
#+attr_latex: :environment tabulary :width \textwidth :align L|RR
Thanks,
Vikas
Bernt Hansen writes:
> I'm fine with removing duplicates in the 1-N list.
Done.
--
Bastien
Hello,
Bastien writes:
> Nicolas Goaziou writes:
>
>> Thinking more about it, I think I need to make some more exceptions
>> anyway. For example timestamps in clock lines and in planning info
>> shouldn't react to `org-export-with-timestamps' (it would be silly to
>> have `org-export-with-plann
Hi Eli,
On Fri, Apr 12, 2013 at 09:38:47PM +0300, Eli Zaretskii wrote:
> > Date: Fri, 12 Apr 2013 20:00:56 +0200
> > From: Suvayu Ali
> > Cc: Torsten Wagner , emacs-orgmode@gnu.org,
> > carsten.domi...@gmail.com
> >
> > If some package wants to keep something updated (line number displays in
Hi Marcel,
Marcel van der Boom writes:
> When exporting a subtree, I often use the attach functionality (C-c C-a)
> to "attach" files to a heading. This gives the heanding an :ATTACH: tag.
>
> When exporting such a subtree via latex to pdf, using
> org-export-dispatch (C-c e) the output in pdf c
Hi Derek,
Derek Upham writes:
> I tried running org-timeline on an Org file with lots of timestamped
> TODO -> DONE state changes, and didn't see the matches I was expecting.
> While poking around, I found two problems.
I finally fixed those. Thanks for reporting this.
--
Bastien
* 42 147 wrote:
>
> Hello mailing list,
Hi!
> The question is the title: have you been able to convert many people to
> Emacs / org-mode?
I am not quite sure how many people actually switched to
Emacs/Org-mode. However, I have seen many open mouths by showing
simply the basic (tables, babel, ..
Aditya Mandayam writes:
> so - has anyone tried something like this before? i thought this would
> be legion. how would you go about implementing this?
I doubt so and for a good reason: it opens the door for potential
security problems.
On the Internet, nobody knows you're a dog; and nobody k
* Suvayu Ali wrote:
>
> Personally I think, any attempts at conversion is futile.
I agree only for cases, where the person does not have issues with
the current editor/workflow.
> Just like real religion, choosing an editor is an immensely
> personal decision if editing text (in whatever form,
* Christian Moe wrote:
>
> Hi,
Hi!
> I cannot replicate Karl's problem. I copied the code examples, and got
> the right results on Org 8.0-pre (pulled this morning).
>
> I did have to make one change -- Babel wouldn't recognize the variables
> until I passed them with :var rather than in parens
Achim Gratz writes:
> Feng Shu writes:
>> org-version: 8.0-pre (release_8.0-pre-416-gbf338e)
>> makeinfo --no-split org.texi -o org
>> org.texi:8719: No closing brace for footnote `'.
>> org.texi:8719: Unmatched }.
>> makeinfo: Removing output file `org' due to errors; use --force to preserve.
>>
And I still mean #+attr_ latex: :width :) You're still missing a colon.
John
On Apr 12, 2013 7:48 PM, "Vikas Rawal"
wrote:
>
> Sorry, I meant:
>
> #+attr_latex :width \textwidth
>
> Vikas
>
>
>
37 matches
Mail list logo
