suvayu ali wrote:
> Hi Seb,
>
> On Mon, Aug 8, 2011 at 8:13 AM, Sebastien Vauban
> wrote:
> > For the sake of completeness, please know you can use PDFLaTeX and UTF-8 --
> > I
> > do it for all my documents -- by having "\usepackage[utf8x]{inputenc}"
> > inserted at the right place(TM).
> >
>
On Mon, Aug 8, 2011 at 9:09 AM, Nick Dokos wrote:
> C-h v org-export-latex-inputenc-alist RET says:
>
>
Thank you Nick, works great now. :)
--
Suvayu
Open source is the future. It sets us free.
On Fri, Aug 5, 2011 at 7:13 PM, Eric Schulte wrote:
> Rainer M Krug writes:
>
> > Hi
> >
> > I have an R package in org, and would like to tangle it before I submit
> to
> > svn.
> >
> > I commit via a code block:
> >
> > #+begin_src sh :results output
> > svn commit -m "edits"
> > #+end_src
>
Hi,
org exports inlinetasks to HTML as preformatted text, and uses the
style class inlinetask. I wanted to export inlinetasks as a section
("div" ?) but with the same style.
I don't know any HTML, but with some guess work I customised the html
template like this:
(html "%s%s%s"
'(
Hi LanX,
LanX wrote:
> Thanks for the suggestion, but the problem persists!
You see it's easier with an ECM...
> Only replacing the "0" with an "a" helps.
I don't have that problem. I guess it must have been fixed recently. It
clearly is related to [0] being interpreted as a footnote reference.
"Sebastien Vauban" writes:
> having "\usepackage[utf8x]{inputenc}" inserted
Please beware that utf8x is part of the obsolete and unsupported ucs
package. As ucs deeply affects the LaTeX kernel, more and more modern
packages are incompatible with utf8x and ucs (csquotes,
hyperref,...). For proper
Hi
for different files, I put different things in the post-tangle hook. At tha
moment, I have an emacs-lisp code block, which I evaluate before I tangle,
but I forget this sometimes - so y question: is it possible (and think to
remember that it is, but I can't find how) to evaluate a source code b
I'm new to orgmode and emacs.
I have downloaded emacs 23.3 for XP and trying to use orgmode that
comes bundled with this version of emacs.
I'm following this tutorial:
http://orgmode.org/worg/org-tutorials/orgtutorial_dto.html
When I mark a project as "Done" it doesn't show the "CLOSED" and date
suvayu ali writes:
> Hi,
>
> org exports inlinetasks to HTML as preformatted text, and uses the
> style class inlinetask. I wanted to export inlinetasks as a section
> ("div" ?) but with the same style.
>
> I don't know any HTML, but with some guess work I customised the html
> template like this
Hi Stefan,
On Mon, Aug 8, 2011 at 9:53 AM, Stefan Nobis wrote:
> For proper Unicode support its preferable to use LuaTeX
> or XeTeX rather than using ucs
Thanks for the warning. :)
--
Suvayu
Open source is the future. It sets us free.
Hi Jambu,
On Mon, Aug 8, 2011 at 10:39 AM, Jambunathan K wrote:
> Put your html file in nxml-mode and do a C-c C-n. You will know the
> reason. Basically it produces an invalid xhtml.
>
> --8<---cut here---start->8---
>
> Questions:
> Detector effects
>
Hello,
Jeff Horn writes:
> Should org-refile be able to refile list items?
Extending `org-refile', or creating an equivalent function for list
items would be overkill, in my opinion.
Just kill the item, repair the list, move point to an appropriate place,
and paste the item there.
Regards,
-
suvayu ali writes:
> Hi Jambu,
>
> On Mon, Aug 8, 2011 at 10:39 AM, Jambunathan K wrote:
>> Put your html file in nxml-mode and do a C-c C-n. You will know the
>> reason. Basically it produces an invalid xhtml.
>>
>> --8<---cut here---start->8---
>>
>> Questi
Chris Henderson writes:
> I'm new to orgmode and emacs.
>
> I have downloaded emacs 23.3 for XP and trying to use orgmode that
> comes bundled with this version of emacs.
>
> I'm following this tutorial:
> http://orgmode.org/worg/org-tutorials/orgtutorial_dto.html
>
> When I mark a project as "Do
Hi Jambunathan,
On Mon, Aug 8, 2011 at 12:35 PM, Jambunathan K wrote:
>
> May be there is no entry for inlinetask in the default css. For example,
> if I add the following to css, I see the entry correctly formatted.
>
[...]
>
> Btw, you can get the div without any of the xhtml syntactic mess w
Hi,
I've noticed that org-add-planning-info adds a superfluous space
character when a repeated task is marked as DONE and gets rescheduled.
Example:
* TODO foo
SCHEDULED: <2011-08-08 Mon +1d>
This becomes (after pressing Shift-Right a few times):
* TODO foo
SCHEDULED: <2011-08-09 Tue +1d>
Hello Orgers,
I wanted to do some preprocessing based on headline tags (set some
properties), before export[1]. But I want to do this only for specific
backends (html/latex). How can I achieve this?
Footnotes:
[1] IIUC I have to customise the `org-export-preprocess-hook'?
--
Suvayu
Open sourc
Jeff Horn writes:
> Would someone throw me a bone? I couldn't find anything on gmane, but
> I my gmane-fu isn't the strongest. :D
>
> On Sat, Aug 6, 2011 at 14:54, Jeff Horn wrote:
>> Should org-refile be able to refile list items? I suspect it would be
>> non-trivial to add this functionality i
Summary: org-inlinetask produces invalid xhtml
The org file and exported html files are included. Org file also
contains some annotation on the bug.
Food for thought: If inline task entry is seen as a regular "body text"
even though it is wrapped in to " " element does that suggest
a possible wa
Nicolas,
> Summary: org-inlinetask produces invalid xhtml
>
> The org file and exported html files are included. Org file also
> contains some annotation on the bug.
>
> Food for thought: If inline task entry is seen as a regular "body text"
> even though it is wrapped in to " " element does that
Suvayu / Others
> Looks like I need to create an entry in
>
> C-h v org-inlinetask-export-templates.
Are there any opinions/preferences on how inline tasks could be exported
in to odt format. I think having an ability to quickly navigate through
all the inline tasks in the exported document woul
On Fri, Aug 5, 2011 at 6:34 PM, suvayu ali wrote:
> Hi John,
>
> On Sat, Aug 6, 2011 at 12:15 AM, John Hendy wrote:
>> 1) writing a script that could handle the failure and leave the
>> current agenda exported text file if it happened
>>
>
> Do you run into the same problem if you one the file be
Hi Jambu,
On Mon, Aug 8, 2011 at 7:00 PM, Jambunathan K wrote:
>
> Suvayu / Others
>
>> Looks like I need to create an entry in
>>
>> C-h v org-inlinetask-export-templates.
>
> Are there any opinions/preferences on how inline tasks could be exported
> in to odt format. I think having an ability t
Hello,
Jambunathan K writes:
>> Summary: org-inlinetask produces invalid xhtml
I've pushed a fix. Is it correct now?
> Additional Note: I think instead of having templates one could have
> org--format-inlinetask(heading task todo priority whatever)
Not as long as org-inlinetask isn't loaded b
Hi John,
On Mon, Aug 8, 2011 at 8:12 PM, John Hendy wrote:
>> Do you run into the same problem if you one the file before hand in
>> read only mode? Something like this before the agenda command might
>> work.
>>
>> (find-file-read-only "FILENAME")
>
> How would I do this via the command line? Al
Hello,
Florian Beck writes:
> (defun org-get-item (&optional kill)
> "Copy the item at point to the kill ring.
> Optionally, kill it."
> (save-excursion
> (let ((beg (org-in-item-p)))
> (org-end-of-item)
> (funcall (if kill
> 'kill-region
>'co
On Mon, Aug 8, 2011 at 1:28 PM, suvayu ali wrote:
> Hi John,
>
> On Mon, Aug 8, 2011 at 8:12 PM, John Hendy wrote:
>>> Do you run into the same problem if you one the file before hand in
>>> read only mode? Something like this before the agenda command might
>>> work.
>>>
>>> (find-file-read-only
Hi John,
On Mon, Aug 8, 2011 at 8:53 PM, John Hendy wrote:
>> If you can use wildcards to specify your files, it might be possible by
>> just one extra call to --eval. Something like this might work:
>>
>> emacs --batch -l ~/.emacs --eval '(find-file-read-only "" t)' \
>> --eval '(org-batch-
On Mon, Aug 8, 2011 at 1:59 PM, suvayu ali wrote:
> Hi John,
>
> On Mon, Aug 8, 2011 at 8:53 PM, John Hendy wrote:
>>> If you can use wildcards to specify your files, it might be possible by
>>> just one extra call to --eval. Something like this might work:
>>>
>>> emacs --batch -l ~/.emacs --eva
Hi,
lines in example blocks are currently indented like the surrounding
begin and end delimiters. ¨This works fine unless, you want to indent
some lines manually; in this case, auto-indenting the buffer reverts
the manual indentation. This patch should prevent this from happening.
Best regards,
Hi John,
On Mon, Aug 8, 2011 at 9:48 PM, John Hendy wrote:
> -batch -l ~/.emacs -eval
Your problem is the long options are wrong. According to the manpages,
there should be 2 hyphens.
--eval and --batch.
GL
--
Suvayu
Open source is the future. It sets us free.
On Mon, Aug 8, 2011 at 3:22 PM, suvayu ali wrote:
> Hi John,
>
> On Mon, Aug 8, 2011 at 9:48 PM, John Hendy wrote:
>> -batch -l ~/.emacs -eval
>
> Your problem is the long options are wrong. According to the manpages,
> there should be 2 hyphens.
>
> --eval and --batch.
Well, that might be *a* p
suvayu ali wrote:
> Hi John,
>
> On Mon, Aug 8, 2011 at 9:48 PM, John Hendy wrote:
> > -batch -l ~/.emacs -eval
>
> Your problem is the long options are wrong. According to the manpages,
> there should be 2 hyphens.
>
> --eval and --batch.
>
Nope - emacs recognizes both (presumably the sing
John Hendy wrote:
> On Mon, Aug 8, 2011 at 1:59 PM, suvayu ali
> wrote:
> > Hi John,
> >
> > On Mon, Aug 8, 2011 at 8:53 PM, John Hendy wrote:
> >>> If you can use wildcards to specify your files, it might be possible by
> >>> just one extra call to --eval. Something like this might work:
> >>
Hello,
Valentin Wüstholz writes:
> lines in example blocks are currently indented like the surrounding
> begin and end delimiters. ¨This works fine unless, you want to indent
> some lines manually;
You may use colons instead. They are meant for this task. I.e.:
: some text
: ^
> in this c
Hi!
I'd like to create a link like
[[file:~/share/all/org-mode/contacts.org::*foo][company:foo]]
... and therefore I created:
,[ ~/snippets/org-mode/vkcomp ]
| # name : expand link to company
| # --
| [[file:~/share/all/org-mode/contacts.org::*$1][company:$1]] $0
`
But: unfortunately
On Mon, Aug 8, 2011 at 3:37 PM, Nick Dokos wrote:
> John Hendy wrote:
>
>> On Mon, Aug 8, 2011 at 1:59 PM, suvayu ali
>> wrote:
>> > Hi John,
>> >
>> > On Mon, Aug 8, 2011 at 8:53 PM, John Hendy wrote:
>> >>> If you can use wildcards to specify your files, it might be possible by
>> >>> just o
Hi Nicolas.
On Mon, Aug 8, 2011 at 10:40 PM, Nicolas Goaziou wrote:
> Hello,
>
> Valentin Wüstholz writes:
>
>> lines in example blocks are currently indented like the surrounding
>> begin and end delimiters. ¨This works fine unless, you want to indent
>> some lines manually;
>
> You
John Hendy wrote:
> On Mon, Aug 8, 2011 at 3:37 PM, Nick Dokos wrote:
> > John Hendy wrote:
> >
> >> On Mon, Aug 8, 2011 at 1:59 PM, suvayu ali
> >> wrote:
> >> > Hi John,
> >> >
> >> > On Mon, Aug 8, 2011 at 8:53 PM, John Hendy wrote:
> >> >>> If you can use wildcards to specify your files,
On Mon, Aug 8, 2011 at 4:09 PM, Nick Dokos wrote:
> John Hendy wrote:
>
>> On Mon, Aug 8, 2011 at 3:37 PM, Nick Dokos wrote:
>> > John Hendy wrote:
>> >
>> >> On Mon, Aug 8, 2011 at 1:59 PM, suvayu ali
>> >> wrote:
>> >> > Hi John,
>> >> >
>> >> > On Mon, Aug 8, 2011 at 8:53 PM, John Hendy w
Hi Nick,
On Mon, Aug 8, 2011 at 10:37 PM, Nick Dokos wrote:
>> > As far as I know, emacs accepts any wildcard that is valid in the shell.
>> > Since all your files are in ~/org, I would say try "~/org/*.org". The
>> > '~/org/' limits it to files within your org directory and the '*.org'[1]
>> > l
Hi John,
On Mon, Aug 8, 2011 at 9:48 PM, John Hendy wrote:
>
> emacs -batch -l ~/.emacs -eval '(find-file-read-only "~/org/*.org" t)' \
> -eval '(org-batch-agenda "e")' > ~/org/aux/agenda-export.txt
>
As I understand, with the above command the wildcard works but the file
locking prevents yo
suvayu ali wrote:
> Hi Nick,
>
> On Mon, Aug 8, 2011 at 10:37 PM, Nick Dokos wrote:
> >> > As far as I know, emacs accepts any wildcard that is valid in the shell.
> >> > Since all your files are in ~/org, I would say try "~/org/*.org". The
> >> > '~/org/' limits it to files within your org dir
Valentin Wüstholz writes:
> Colons are great for short snippets. However, blocks are far more
> convenient for longer passages.
That's certainly true, but I fail to see an use case for such long
passages. May I know what you do have in mind?
> What potential hassle were you thinking of?
Being
Thanks to Florian for sharing code. Nicolas, I still think this is a
bug. I don't doubt extending org-refile would be messy. It's above my
head, and I realize I'm asking a lot from anyone that would tackle
this for me, but I still think its a bug. Your workaround sounds
exactly like what org-refile
Jeff Horn writes:
> Thanks to Florian for sharing code. Nicolas, I still think this is a
> bug. I don't doubt extending org-refile would be messy. It's above my
> head, and I realize I'm asking a lot from anyone that would tackle
> this for me, but I still think its a bug.
Where is the bug? As f
On Mon, Aug 8, 2011 at 19:03, Nicolas Goaziou wrote:
> Jeff Horn writes:
>
> Where is the bug? As far as I can see, you're expecting a function
> designed for headlines only to operate on list items. Am I missing the
> point?
I'm approaching this as a user. I've made one contribution to this
pro
Jeff Horn wrote:
> So, as a user, I was expecting something to happen that didn't. That's
> a bug. That may be a misuse of the term, and I apologize for using it
> loosely.
>
It's a bug all right: the question is whether the bug is in the code,
in the docs or in the user's head ;-) 99.9% of the
Jeff Horn wrote:
> > What would be the specifications of that function? Would it only send
> > the item at point to the end of the headline specified through the
> > refile interface?
>
> I hope its clear that this is all above my head. I know enough to make
> suggestions, but not contribute to
On Mon, Aug 8, 2011 at 20:20, Nick Dokos wrote:
> Jeff Horn wrote:
>
>> > What would be the specifications of that function? Would it only send
>> > the item at point to the end of the headline specified through the
>> > refile interface?
>>
>> I hope its clear that this is all above my head. I k
On Mon, Aug 8, 2011 at 20:40, Jeff Horn wrote:
> I see, thanks Nicholas. As a start, in a subjectively ideal world,
> org-refile-list-item would work on list items:
>
> 1) and their children to arbitrary depth
> 2) in the current buffer, or any agenda file
> 3) using either path-like headline spec
Jeff Horn writes:
>> What would be the specifications of that function? Would it only send
>> the item at point to the end of the headline specified through the
>> refile interface?
>
> I hope its clear that this is all above my head. I know enough to make
> suggestions, but not contribute to im
On Tue, Aug 9, 2011 at 2:02 AM, Nick Dokos wrote:
> 99.9% of the bugs I find are
> in my head (most recently the find-file wildcard thing...)
>
I think you can let that go now :D
> Nick
--
Suvayu
Open source is the future. It sets us free.
Hi Nicolas,
thanks for the quick response.
On Tue, Aug 9, 2011 at 12:33 AM, Nicolas Goaziou wrote:
> Valentin Wüstholz writes:
>
>> Colons are great for short snippets. However, blocks are far more
>> convenient for longer passages.
>
> That's certainly true, but I fail to see an use case for
Nicolas Goaziou writes:
> Hello,
>
> Jambunathan K writes:
>
>>> Summary: org-inlinetask produces invalid xhtml
>
> I've pushed a fix. Is it correct now?
The problem persists. You can put the exported html file in nxml-mode
and do a C-c C-n to find the validation errors.
I am attaching the two
55 matches
Mail list logo
