Greetings.
Nicolas Goaziou writes:
>> +;; This differs from most standard languages in that
>> +;;
>> +;; 1) there is no such thing as a "session" in processing
>> +;;
>> +;; 2) results can only be exported as html; in this case, the
>> +;;processing code is embedded via a file into a javas
On Mon, 30 Mar 2015, at 18:08, Marco Wahl wrote:
> Peter Westlake writes:
>
> > On Mon, 30 Mar 2015, at 17:54, Marco Wahl wrote:
> >> Hi Peter,
> >>
> >> Peter Westlake writes:
> >>
> >> > Thanks for the suggestion, but this doesn't make the bug go away for
> >> > me.
> >>
> >> That's awkward
On Saturday, 28 Mar 2015 at 10:53, Richard Lawrence wrote:
> Hi everyone,
>
> I thought I should send an update to let you know that org-citeproc [1],
> the command-line citation processing tool I've been working on, now
> supports multi-cites. I believe that means it is now capable of
> processin
Florian Beck writes:
> Seems like this does trick. I don't really understand why, though.The
> previous profiling seemed to indicate that most of the time was spent in
> `org-entry-get' (that's why I removed it).
`org-entry-get' is quite fast by itself. However it was called on every
entry with
Hello,
Thierry Banel writes:
> Ok, 100% of votes are for the removal of wired #includes.
> Here is the patch. Tests are changed accordingly.
Applied. Thank you.
>> IMO, it would be better than the current situation, but I wonder if
>> it makes sense to have a global default setting containing
Rasmus writes:
> Nicolas Goaziou writes:
>
>>> So I would keep them. The documentation explicitly states which backend
>>> these keywords are supported by.
>>
>> OK. Then DESCRIPTION and KEYWORD stay in "ox.el", and documented in
>> "Export settings". You need to revert your patch about it.
>
>
Rasmus writes:
> Nicolas Goaziou writes:
>
>> Also, assuming you keep :subtitle instead of :BACKEND-subtitle, these
>> should also be documented in Publishing options.
>
> So I *still* don't see this. I assume you want me to add something do you
> want me to add lines like this:
>
> @item
I am attempting again to write a latex document with org-mode. The
org-mode part is no problem, but the latex part is awkward. This is
the first few line of my org-mode document -
--8<---cut here---start->8---
#+TITLE: The history of custard pies.
#+AUTHOR:
Hello,
In one of my Org files, I have 20 small tables. Among them, 11 have
a line of formula's (TBLFM), mainly for computing a total (sum), so
that's in essence relatively standard and simple.
The file in itself is quite big (11,000 lines), but I did not expect to
see that re-applying formulas to
Hello,
Sharon Kimble writes:
> I am attempting again to write a latex document with org-mode. The
> org-mode part is no problem, but the latex part is awkward. This is
> the first few line of my org-mode document -
>
>
> #+TITLE: The history of custard pies.
> #+AUTHOR:Sharon Kimble
> #+
Hi,
Nicolas Goaziou writes:
> As I explained, both are linked:
>
> - Anything defined in "ox.el" is documented in "Export settings" ;
> - Anything defined in "ox-backend.el" is documented in "Backend
> export".
>
> This is a hard rule.
OK.
> Even if it means repeating documentation in
Sharon Kimble writes:
> #+LATEX: \usepackage{~/texmf/tex/latex/commonstuff/mysty}
> # #+Latex_Class: mysty
Use #+latex_header.
—Rasmus
--
Together we will make the possible totay impossible!
Hello,
Eric Abrahamsen writes:
> Subject: [PATCH] org-mime.el: Avoid use of letf/cl-letf
Thank you. Some comments follow.
> +(let* ((mp (lambda (p)) (org-entry-get nil p
> org-mime-use-property-inheritance))
It should be
(mp (lambda (p) (org-entry-get )))
> + (let ((bhook
> +
Rasmus writes:
>> For the record, if the situation ever rises again, I think that
>> a keyword can be added to "ox.el" only if
>>
>> - it is supported at least in every major back-end (ASCII, HTML,
>> LaTeX, ODT and Texinfo)
>> - it comes with a toggle in the OPTIONS line e.g. keyword:nil
Sebastien Vauban
writes:
> Hello,
>
> In one of my Org files, I have 20 small tables. Among them, 11 have
> a line of formula's (TBLFM), mainly for computing a total (sum), so
> that's in essence relatively standard and simple.
>
> The file in itself is quite big (11,000 lines), but I did not exp
Sebastien Vauban
writes:
> Hello,
>
> In one of my Org files, I have 20 small tables. Among them, 11 have
> a line of formula's (TBLFM), mainly for computing a total (sum), so
> that's in essence relatively standard and simple.
It looked like like Gnus failed when sending my reply the last time,
Hi
I am using tabbar (I know - I am one of the strant=ge folk=s who use the
mouse...) and whenever I edit code, the tabbar is overwritten by the top
bar which says "Edit, then exit with ..." (I'll just call it the "info bar").
Here is a screenshot which shows on the right window the tabbar, and o
Jacob Nielsen wrote:
> Sebastien Vauban writes:
>>
>> In one of my Org files, I have 20 small tables. Among them, 11 have
>> a line of formula's (TBLFM), mainly for computing a total (sum), so
>> that's in essence relatively standard and simple.
>
> Try this:
> # -*- cache-long-scans: nil; -*-
> #
Wow, that was way easier than I thought it would be. Made a couple of
modest changes to org-html-to-html, and now a simple keybinding exports to
my desired location and opens the file in my desired location, which I
purge every couple of days. Thank you!
On Sat, Mar 28, 2015 at 11:43 AM, Nicolas
On 2015-03-20 at 13:53, Samuel Wales wrote:
> hmm:
>
> ===
> search-invisible is a variable defined in `isearch.el'.
> Its value is open
>
> Documentation:
> If t incremental search/query-replace can match hidden text.
> A nil value means don't match invisible text.
> When the value is `open', if
I have a custom agenda view that includes the today view:
(agenda "" ((org-agenda-ndays 1)
(org-agenda-overriding-header "Scheduled Today")
(org-deadline-warning-days 0)))
And the next week:
(agenda "" ((org-agenda-overriding-header "Scheduled")
(org-de
Hello,
Nick Dokos writes:
> Trying to just read Xavier's email message in Gnus, I get the following
> backtrace (with unprintable characters replaced by periods) - to me, this
> looks like a bug somewhere, but not sure where:
>
> Debugger entered--Lisp error: (error "Before first headline at pos
Hi,
Following this discussion:
Nicolas Goaziou writes:
> Rasmus writes:
>> OK. So with the above the in mind the game plan [for documentation]
>> seems to be:
>>
>> - Remove DESCRIPTION/KEYWORD from it's current position in org.texi
>>to backend descriptions and retain them in re
On 2015-03-31, at 12:26, Sharon Kimble wrote:
> I am attempting again to write a latex document with org-mode. The
> org-mode part is no problem, but the latex part is awkward. This is
> the first few line of my org-mode document -
>
> --8<---cut here---start-
Hi all,
the following function has served me well for a few years, so I thought
I'd share it. I would even be happy to contribute it to the codebase of
org-mode (core or contrib); however in this case someone would have to
point me to a fool-proof guide for how to do this. I know that for
c
Dear org-mode community,
I use org's clocking facility to clock all my working time. I
frequently find myself clocking time for a task T1, but later realise
that I actually spent part of this time on some other task T2. In such
a situation I go to the corresponding CLOCK: line for T1, split
On Tuesday, 31 Mar 2015 at 12:36, Rasmus wrote:
> Sharon Kimble writes:
>
>> #+LATEX: \usepackage{~/texmf/tex/latex/commonstuff/mysty}
>
> Use #+latex_header.
And possibly omit the full path as LaTeX should be able to find
mysty.sty if located within the ~/texmf directory. (untested)
--
: Er
On 2015-03-31, at 18:54, Eric S Fraga wrote:
> On Tuesday, 31 Mar 2015 at 12:36, Rasmus wrote:
>> Sharon Kimble writes:
>>
>>> #+LATEX: \usepackage{~/texmf/tex/latex/commonstuff/mysty}
>>
>> Use #+latex_header.
>
> And possibly omit the full path as LaTeX should be able to find
> mysty.sty
Hi Eric and all,
Eric S Fraga writes:
> On Saturday, 28 Mar 2015 at 10:53, Richard Lawrence wrote:
>> I thought I should send an update to let you know that org-citeproc [1],
>> the command-line citation processing tool I've been working on, now
>> supports multi-cites. I believe that means it
Hello!
Is it possible to create timestamps (SCHEDULED:) for TODOs with respect to one
timezone, but have Agenda view show them for another zone — so that when I move
to another timezone, all I have to do is tell org-mode (via environment?) in
which timezone I happen to be at the moment, to have
Hi
Steps to reproduce:
- if org-descriptive-links is non-nil, invoke M-x org-toggle-link-display
- org-descriptive-links is now expected to be nil
- M-x org-agenda-list
- M-x org-agenda-clockreport-mode (or short: v R)
Observation (given that there is at least some data being shown in the
clockr
Richard Lawrence writes:
> However, there are a couple of other scenarios to think about:
>
> 1) Some people may still need to use plain BibTeX. Generating LaTeX
> that is intended to be processed with BibTeX, as opposed to BibLaTeX, is
> a little trickier, because (IIUC) BibTeX does not support
Le 31/03/2015 12:07, Nicolas Goaziou a écrit :
>
>> IMO, it would be better than the current situation, but I wonder if
>> it makes sense to have a global default setting containing the
>> three files, but one which the user can customize; any :includes
>> parameters would augment the default.
>>
>
Hello,
Christoph LANGE writes:
> the following function has served me well for a few years, so
> I thought I'd share it. I would even be happy to contribute it to the
> codebase of org-mode (core or contrib); however in this case someone
> would have to point me to a fool-proof guide for how to
hi ken,
that's right, my point was that perhaps it is relevant, not that one
would set the variable.
for example, perhaps there is a way that timestamps can have an
invisible property and thus be subject to this variable.
of course, it might not be possible, if timestamps do not use
overlays, bu
Aloha all,
Nick Dokos writes:
> Richard Lawrence writes:
>
>> However, there are a couple of other scenarios to think about:
>>
>> 1) Some people may still need to use plain BibTeX. Generating LaTeX
>> that is intended to be processed with BibTeX, as opposed to BibLaTeX, is
>> a little trickie
Rasmus writes:
> An example of a structure change is attached. It introduces a table
> similar to @ref{Export settings} in the beginning of most backend
> chapters.
>
> I have not (re)read it yet, but I want to make sure that we roughly agree
> on the structure before I put more time into it. I
On Mar 31, 2015 9:53 PM, "Nicolas Goaziou" wrote:
> The problem is that we're running out of interesting keybindings.
Let me ask the question differently: as all reasonable key bindings are
taken (a statement to which I tend to agree), is the suggestion of
interactive functions to be added to the
On Tuesday, 31 Mar 2015 at 12:13, Richard Lawrence wrote:
> Hi Eric and all,
>
> Eric S Fraga writes:
[...]
>> However, for some reason, libreoffice doesn't display the citations in
>> the ODT document you have included. I have had a look at the actual ODT
>> file and it looks fine. Can you su
Hi,
Nicolas Goaziou writes:
>> An example of a structure change is attached. It introduces a table
>> similar to @ref{Export settings} in the beginning of most backend
>> chapters.
>>
>> I have not (re)read it yet, but I want to make sure that we roughly agree
>> on the structure before I put m
Hi Tom and all,
t...@tsdye.com (Thomas S. Dye) writes:
>> I know next to nothing about citations in general, so please bear with
>> me: if multi-cite support means being able to condense citations (e.g.
>> [1-3, 5, 9]), then bibtex can do at least some of that
>> (e.g. http://texblog.org/2007/05/
Richard Lawrence writes:
> I don't really know anything about the ODT format, though. My code
> more-or-less blindly pastes Pandoc-generated XML into the document
> during Org ODT export. Can someone who knows more about the format take
> a look at the file and see if there is some subtle probl
Thierry Banel writes:
> Le 31/03/2015 12:07, Nicolas Goaziou a écrit :
>>
>>> IMO, it would be better than the current situation, but I wonder if
>>> it makes sense to have a global default setting containing the
>>> three files, but one which the user can customize; any :includes
>>> parameters
Richard Lawrence writes:
> Hi Tom and all,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>>> I know next to nothing about citations in general, so please bear with
>>> me: if multi-cite support means being able to condense citations (e.g.
>>> [1-3, 5, 9]), then bibtex can do at least some of that
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> Subject: [PATCH] org-mime.el: Avoid use of letf/cl-letf
>
> Thank you. Some comments follow.
>
>> +(let* ((mp (lambda (p)) (org-entry-get nil p
>> org-mime-use-property-inheritance))
>
> It should be
>
> (mp (lambda (p) (or
Ken Mankoff writes:
> I have a custom agenda view that includes the today view:
>
> (agenda "" ((org-agenda-ndays 1)
> (org-agenda-overriding-header "Scheduled Today")
> (org-deadline-warning-days 0)))
>
> And the next week:
>
> (agenda "" ((org-agenda-overriding-head
46 matches
Mail list logo
