Michael Gauland writes:
> Nicolas Goaziou gmail.com> writes:
>> On the other hand, you have a hard-coded macro to solve this problem:
>>
>> #+DATE: {{{time(%c)}}}
>>
>> It will work across every back-end (but you need the latest Org version,
>> sin
T'
keyword doesn't have to. Someone may come up with a broader use case.
For example, it could prevent Babel blocks from being executed.
Regards,
--
Nicolas Goaziou
Hello,
Nick Dokos writes:
> Michael Gauland wrote:
>
>> Nicolas Goaziou gmail.com> writes:
>>
>> > I just tried with a minimal init and it worked. Could you send the
>> > example you're trying to export?
>>
>> The file is below.
Hello,
Achim Gratz writes:
> Nicolas Goaziou writes:
>> {{{date(%c)}}} is another macro that is replaced with the #+DATE: value
>> during export. Since you try to replace #+DATE: value with itself, you
>> dive into an inf loop.
>
> Which raises the question if thi
Michael Gauland writes:
> I think I understand what's going on now, but I'm still at a loss as to
> how to get the date I want. Can I tell the exporter that the date on the
> document should be derived from the current time (or the last
> modification time), formatted a particular way? For exampl
ved-mode-p ...
>> (save-excursion (save-restriction (widen) (if (and ...
>> org-adaptive-fill-function()
>
> FYI, this seems to happen when in an itemized list, not on a regular
> paragraph...
It should be fixed. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Nick Dokos writes:
> Michael Gauland wrote:
>
>> On 30/10/12 22:29, Nicolas Goaziou wrote:
>> > Doesn't
>> >
>> >#+DATE: {{{time(%Y-%m-%d %H:%M)}}}
>> >
>> > get you what you expect?
>>
>> That gives me an e
"Sebastien Vauban"
writes:
> However, after updating to Org-mode version 7.9.2 (release_7.9.2-541-gdda563 @
> d:/home/sva/src/org-mode/lisp/), I have another problem with the exact same
> cause (typing more than 80 characters, or pressing M-q on an itemized
> list):
And here is another take to
Eric S Fraga writes:
> The problem with the inf-loop now makes sense but the documentation
> implies otherwise:
>
> ,
> | Also,
> | `{{{date(FORMAT)}}}' and `{{{modification-time(FORMAT)}}}' refer to
> | current date time and to the modification time of the file being
> `
I changed the d
eporting back errors.
Regards,
--
Nicolas Goaziou
Hello,
Yagnesh Raghava Yakkala writes:
> It would be good if no author command is export. please implement it.
Done. Note: author:nil _and_ email:t will still use the email as the
argument of the author command.
Regards,
--
Nicolas Goaziou
src java
> Why to use a colon in one case and not in the other one? Or am I wrong
> here?
#+INCLUDE: is a keyword, like #+TITLE: whereas #+BEGIN_SRC is a block,
like #+BEGIN_CENTER. Not the same object, not the same syntax.
Regards,
--
Nicolas Goaziou
Fabrice Popineau writes:
> Given the fact that '#+INCLUDE: "file" src java' is expanded into an src
> block,
> I assume that htmlize should apply there too. Am I wrong?
I think you're correct. A quick test shows me fontification is fine. Do
you have an ECM to show the problem?
Regards,
Hello,
Elias Pipping writes:
> Note how there's now a comma that shouldn't be there. That comma is
> never displayed in the mode that is entered through `org-edit-src-code`,
> though.
See section: 11.3 Literal examples. In particular, footnote 4.
Regards,
--
Nicolas Goaziou
nil)))
(key (and (string-match "%\\(:.*\\)" attr-symbol)
(intern (match-string 1 attr-symbol
is better.
Regards,
--
Nicolas Goaziou
example, your code operates only at top-level, i.e. it won't handle
something like:
%(fun arg1 (sub-fun %:description))
It will also error out if any atom isn't a symbol, i.e.:
%(format "%d" 1)
It's all about pro and cons.
Regards,
--
Nicolas Goaziou
but
it isn't hooked into `org-agenda-write' yet. For now, you can test it,
from an agenda buffer, with:
M-: (org-e-icalendar-export-current-agenda)
Feedback is welcome.
Regards,
--
Nicolas Goaziou
ture must be documented in `org-capture-templates'
docstring and org.texi.
Thank you for working on it.
Regards,
--
Nicolas Goaziou
Ryo TAKAISHI writes:
> I fixed and added document in docstring & org.texi.
Thank you.
> + @r{If sexp's attr is link keyword (@code{%:keyword}),}
> + @r{it will be expanded using @code{org-store-link-plist}.}
Documentation should not contain a reference to `org
Hello,
Skip Collins writes:
> When compiling the latest git version with make up2, the end-of-line
> test fails, giving the following output:
This should be fixed on master (and even maint). Could you confirm this?
Thanks for the report.
Regards,
--
Nicolas Goaziou
Hello,
Ryo TAKAISHI writes:
> I create a complete patch for current commit.
I've pushed your patch on master (with some documentation tweaks). Thank
you for your work.
Also, please consider signing FSF papers if you want to make other
contributions to Org.
Regards,
--
Nicolas Goaziou
Hello,
Rafael Laboissiere writes:
> The patch attached below fixes a very minor problem in org-bibtex.el.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
rs and
it should return a string.
We can also provide default functions for current behaviour (i.e.
fractional time and Hs:MM) and for the one you suggest.
It's more work, but it simplifies the whole thing in the end.
What do you think? Do you want to give it a try?
Regards,
--
Nicolas Goaziou
ust "do the right
> thing" in all the cases I listed above. On the other hand, it won't allow
> unusual formats that don't fit the above scheme (but they're not possible
> now, anyway).
>
> Thoughts?
I think it's too much complicated: it requires to know about strange
formatting rules. I suggest to keep it simple: just specify a function
with fixed arguments to do the job and provide default functions to
handle most common cases.
Regards,
--
Nicolas Goaziou
Hello,
Ryo TAKAISHI writes:
> But, I had forgot to escape double quote in docstring, so attach patch
> fixing it.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
ush a fix for it.
Regards,
--
Nicolas Goaziou
Hello,
Toby Cubitt writes:
> I'd prefer to see some agreement before I waste time coding something
> that won't get accepted.
Then let's wait for Achim (Cc'ed) to illustrate what he has in mind,
because his proposal is too vague yet to permit discussion about i
s "org-end-of-line" goes to the end of the real line (it
> ignores soft line breaks). The FAQ says that this used to be broken back
> in 2009, but does not mention this asymmetry. Is this a bug?
This is a bug, which should be fixed now. Could you confirm it?
Thanks for reporting this.
Regards,
--
Nicolas Goaziou
ence,
#+begin_src org
,* Headline
#+end_src
would become
* Headline
just before parser kicks in.
But, again, let's see first if no solution can be found without creating
yet another special case.
Regards,
--
Nicolas Goaziou
[itm]], ...
will be exported as "As one can see in item 2, ...".
Regards,
--
Nicolas Goaziou
to go. Three options in the
defcustom:
- One to provide regular time (i.e 14:40 or 3d 18:32)
- One to provide decimal time with the highest unit available (i.e.
18,75 h or 2,5 d).
- One free slot for an user-defined function.
Regards,
--
Nicolas Goaziou
'regular) ...)
((eq org-duration-format 'decimal) ...)
(t (error "Invalid `org-duration-format' value"
#+end_src
One variable exposed to the user. One function exposed to the developer.
It's much simpler.
Regards,
--
Nicolas Goaziou
ot: custom formats mean parsing hell. So either:
1. We define a new format, non customizable, but possibly conditional,
which can describe a duration, in order to include days.
2. We allow customization as overlays (much like timestamps).
3. We leave it as-is.
I'm not very fond of 2, so I think this whole customization problem is
moot anyway.
Regards,
--
Nicolas Goaziou
Hello,
Toby Cubitt writes:
> Subject line and commit message says it all.
`org-end-of-line' has been patched already. Is there a bug in
`org-beginning-of-line'?
Regards,
--
Nicolas Goaziou
If the generated code doesn't contain an headline, you don't need raw
results.
Regards,
--
Nicolas Goaziou
xt)}}}.
--8<---cut here-------end--->8---
Regards,
--
Nicolas Goaziou
Ista Zahn writes:
> Thank you, all is working as desired now! One small niggle: the
> '::RESULTS:' and ':END:' strings are included in the exported html.
> Not sure if this is intentional, but it seems to me that they should
> be removed (or at lease given a class so we can hide them via css)
Th
patch h o
That's because exporting a marked (or a narrowed, for that matter)
subtree isn't the same as exporting a subtree.
You have to explicitly tell the exporter you're exporting a subtree, so
it can read :EXPORT_OPTIONS: property.
See "Export Scope" option (3) in `org-export-dispatch'.
Regards,
--
Nicolas Goaziou
Hello,
Giovanni Ridolfi writes:
> When I try to HTML export a *subtree*
> with the new exporter I get "\\" if in the org file there is a newline
You need to update Org. I fixed this several days ago.
Regards,
--
Nicolas Goaziou
this variable is a no-op.
Btw, if you plan to patch this area, could you provided tests for it
(see test-org/end-of-line in test-org.el)? As I can testify, there is
a high risk of regression in that area.
Regards,
--
Nicolas Goaziou
Ista Zahn writes:
> On Tue, Nov 6, 2012 at 11:44 AM, Nicolas Goaziou wrote:
>> Ista Zahn writes:
>>
>>> Thank you, all is working as desired now! One small niggle: the
>>> '::RESULTS:' and ':END:' strings are included in the exported html.
Giovanni Ridolfi writes:
> did you try to replicate the bug?
Yes, sir.
I get:
--8<---cut here---start->8---
I am interested in this
2nd
hello UP
hello
Toby Cubitt writes:
> I'm confused. Which variable are you talking about here?
`line-move-visual'
> Anyway, I see that `visual-line-mode's sets `line-move-visual' to t
> buffer-locally. So checking only `line-move-visual' in
> `org-beginning-of-line' is fine...
>
> ...which strongly suggests th
Toby Cubitt writes:
> 4. We replace the existing muddle with two defcustoms, one selecting
>regular or decimal (or user-defined function), and one specifying a
>list of standard format strings that the function can choose between,
>depending on the duration.
>
> No custom format requi
Toby Cubitt writes:
> Aha! You may well be right. In which case why is `org-beginning-of-line'
> doing this:
>
> (if (org-bound-and-true-p line-move-visual)
> (beginning-of-visual-line 1)
> (beginning-of-line 1))
>
> Shouldn't it be doing this instead?
>
> (if (org-bound-and-true-p
Toby Cubitt writes:
> I guess you want regression tests for `end-of-line' with
> `visual-line-mode' enabled? (There aren't any tests for beginning-of-line
> in test-org.el currently, and the fix to org-beginning-of-line won't
> actually change the behaviour, just make the code more correct.)
No,
Toby Cubitt writes:
> I doubt it can be done now, since we already allow user-defined format
> strings.
I'm more focused on what we will be able to do.
> Where are displayed durations formatted with org-time-clocksum-format et
> al. parsed back to a number of minutes in the current code? If the
haracters.
2. to limit the characters allowed in targets and remove
`org-export-solidify-link-text' altogether.
Regards,
--
Nicolas Goaziou
Colons are now allowed in targets.
Thanks for submitting the suggestion.
Regards,
--
Nicolas Goaziou
"%.2fh" "%.2fmin") | (nil 11.3 nil) | 11.30h
|
| 'regular| ("%dd " "%d:" "%02d") | (1 3 5) | 1d 3:05
|
| 'regular| (nil "%d:" "%02d") | (1 3 5) | 27:05
|
We can extend it to years if needed.
Regards,
--
Nicolas Goaziou
or your patch.
Would you mind adding comments in the function in order to explain the
need for two pass. Also, you may want to reverse the if test in order to
get rid of the progn.
Finally, could you provide the patch as "git format-patch" and add
a changelog entry to it?
Regards,
--
Nicolas Goaziou
emplate with
the required headers.
Regards,
--
Nicolas Goaziou
org-export-before-parsing-hook'.
Regards,
--
Nicolas Goaziou
e there
> could be an option for it?
Indeed, there could be a "date:nil" option. I'll add it later. Thanks
for suggesting it.
Regards,
--
Nicolas Goaziou
ent-buffer)))
(org-export-block-preprocess))
I'm Cc'ing Eric Schulte in case he finds time to look at the problem.
Regards,
--
Nicolas Goaziou
think it should be fixed now in master. Could you try again and
confirm it?
Regards,
--
Nicolas Goaziou
; Now I just need to find time to code it up...
Good to hear we eventually settled on a solution !
Regards,
--
Nicolas Goaziou
(setq s (replace-regexp-in-string "/" "/" s))
> +s)
I'd rather nest the `replace-regexp-in-string' instead of setq'ing twice
in a row the same variable. I.e:
(replace-regexp-in-string
"/" "/" (replace-regexp-in-string "" "" s))
Regards,
--
Nicolas Goaziou
bably to the
> 24.3 release branch) and org-mode later. But I thought I'd share the
> patch first.
I think this was fixed a while ago. I'll wait for your feedback after
you update Org.
Regards,
--
Nicolas Goaziou
Hello,
Giovanni Ridolfi writes:
> 2. Otherwise I cannot get the clock line in the HTML file:
[...]
> - with the new exporter
>
> (with or without propertiies)
You may want to use `org-export-with-clocks', or the c:t OPTION item.
Regards,
--
Nicolas Goaziou
Hello,
Takafumi Arakaki writes:
> Do you know if it is fixed in both master and maint, or only in
> master?
I don't know. If it's fixed already, I guess the patch was applied to
maint.
Regards,
--
Nicolas Goaziou
Takafumi Arakaki writes:
> I am not familiar with org-mode test suite but I can try. Could you
> tell me where I can find similar test cases which creates archive
> entries?
We use ERT.
There is no test case related to archive entries yet. Though, if you
write a recipe to reproduce a problem,
Takafumi Arakaki writes:
> I thought it would be convenient if there was a macro or something to
> setup temporal main org file and temporal archive file. If there is
> nothing like that, then I will just create by my self or use
> unwind-protect or something directly.
>
> I remember there is a
-moz-transform: rotate(90deg);
> -o-transform: rotate(90deg);
> -webkit-transform: rotate(90deg);
> background-color: #EFEFEF;
> }
> #+end_src
It looks like a bug in htmlize, not in Org.
Regards,
--
Nicolas Goaziou
atch.)
It's better if you can provide a changelog entry and send it with "git
format-patch". Also, if you did not sign FSF papers, you will have to
add "TINYCHANGE" at the end of the change log.
Thank you.
Regards,
--
Nicolas Goaziou
Peter Salazar writes:
> Is there a way to get clock items to display in 12-hour format? At least in
> the HTML export?
You could use `org-display-custom-times' variable, with
`org-time-stamp-custom-formats' set accordingly.
Note that if you don't want to toggle the custom time display globally,
Alan Schmitt writes:
> I'll do this when I get back near a computer.
Great.
> Also, about the FSF papers, is there a link for this procedure?
Certainly: http://orgmode.org/worg/org-contribute.html (in particular
the second section, but the whole page in interesting).
It basically boils down t
Peter Salazar writes:
> Great! And how should I specify org-time-stamp-custom-formats in order to
> display 12-hour times?
>
> Default is this, which displays 24-hour times:
>
> ("<%m/%d/%y %a>" . "<%m/%d/%y %a %H:%M>")
According to `format-time-string' docstring, something like:
("<%m/%d/%y
Alan Schmitt writes:
> Attached.
Applied (with a slight twist). Thank you.
I've added you to the list of contributors without FSF assignment. Tell
me once you have signed them.
> With another question: should the patch be sent to the list,
> or just to you (or any other process)?
Please send
hough.
Regards,
--
Nicolas Goaziou
Peter Salazar writes:
> Wait, I was wrong—adding the c:t OPTION actually did not solve the problem.
> I forgot I had converted my clock-in and clock-out to plain text in an
> attempt to work around the problem, so it appeared to work only because it
> was plain text. Apologies.
I was talking abo
d--->8---
Do you use the latest Org? Is it specific to R, or can you reproduce my
example?
Regards,
--
Nicolas Goaziou
e example given in "Calendar/Diary integration" section is
outdated, as it relies on CATEGORY keyword to change category on the fly
within the same section (see footnote in 10.4.1).
--
Nicolas Goaziou
in the table.
That's because inline src blocks are not allowed in table cells.
Appropriate place for formulas in the spreadsheet is the TBLFM line.
Regards,
--
Nicolas Goaziou
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> #+EXPORT_SELECT_TAGS: export
> #+EXPORT_EXCLUDE_TAGS: noexport
This should be (see `org-export-options-alist'):
#+SELECT_TAGS: export
#+EXCLUDE_TAGS: noexport
Regards,
--
Nicolas Goaziou
Peter Salazar writes:
> Oh cool. How do I install the new exporter? I don't use git.
You can use package.el, for example and install org-plus-contrib package
(new exporter is in contrib/ directory). See:
http://orgmode.org/elpa.html
Regards,
ph(g,1,2),p);
xaxis(xmax=2.3,Ticks(Size=1mm,NoZero),Arrow(6pt));
yaxis(ymax=1.3,Ticks(step=.5,Step=1,Size=1mm,NoZero),Arrow(6pt));
label("$O$",(0,0),SW);
label("$C_f$",(1.5,g(1.5)),2N,p);
#+END_SRC
#+BEGIN_CENTER
#+RESULTS: app
[[file:application.pdf]]
#+END_CENTER
Regards,
--
Nicolas Goaziou
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> Patch attached.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
:
> #+XSLT:
>
> * Export
>
> * Do not export:noexport:
>
> Exports:
>
> ...
>
> @menu
> * Export::
> * Do not export::
>
> @end menu
>
> ...
This should be fixed now. Thank you for reporting it.
Regards,
--
Nicolas Goaziou
gs" mechanism, directly at the plain text transcoded (see
`org-e-latex-plain-text' for example).
Regards,
--
Nicolas Goaziou
'll hack on this myself and come
> back eventually.
You can tweak `org-e-icalendar-include-body' (i.e. set it to nil).
Regards,
--
Nicolas Goaziou
unctionality, so you shouldn't be missing anything.
Regards,
--
Nicolas Goaziou
t; I guess the #3 is the culprit. Any idea what went wrong?
To sum it up, I added :parent property to each string but org-e-publish
tries to store them in the cache, which is impossible since cache is
eventually written to a file.
I have pushed a fix for that problem. Is it correct now?
Thanks for submitting this.
Regards,
--
Nicolas Goaziou
Hello,
Peter Münster writes:
> * TODO test
> bla bla bla
> DEADLINE: <2012-11-08 Thu 12:17>
In Org, planning info (scheduled, deadline, and closed) must be put just
after the headline. Your example isn't valid.
Regards,
--
Nicolas Goaziou
nitial and boundary conditions blah blah.
The line starts with a number followed by a dot and a space. This is the
definition of an Org plain list starter.
Note that this result is impossible to obtain with filling or
auto-filling, so you probably put it here manually.
Regards,
--
Nicolas Goaziou
to me. Perhaps the closing brace is removed later?
You should not bother too much about it, footnotes in tables are not
supported directly by LaTeX anyway.
Regards,
--
Nicolas Goaziou
he overhead of generating the diary first. There are not meant
to be used as a replacement for timestamps.
Regards,
--
Nicolas Goaziou
wing an item, that is not
often enough, IMO, to make it unsurprising.
Regards,
--
Nicolas Goaziou
symbols. So, yes, this is the expected behaviour.
Note that you can also have a non-breaking space by using an entity:
\nbsp{}.
Regards,
--
Nicolas Goaziou
tion. The
question is: why doesn't it kick in here?
Did you try with -Q? Also, what is the value of `fill-nobreak-predicate'
variable in that buffer?
Regards,
--
Nicolas Goaziou
x27;). Internally
it uses the function `org-diary-to-ical-string', but, last time I tried,
this function wasn't able to return anything but the empty string. YMMV.
Regards,
--
Nicolas Goaziou
' and
`org-fill-line-break-nobreak-p' functions. Do you have an idea why it
doesn't?
Regards,
--
Nicolas Goaziou
ters with his Groff backend. You may want to try it.
Anyway, for the record, I'm posting an updated version[1] of the file,
compatible with latest Org (master branch). It may solve your problem.
Regards,
[1] I do not seriously maintain this file. It was a proof of concept.
--
Nicolas Goazi
latex.el file may be changed
> some other time, if needed.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Andreas Leha writes:
> Good suggestion. I did, and org-export is the guilty one.
>
> Should that be loaded before?
You should try to update Org and try again. I just commited a patch
which should fix the issue.
Regards,
--
Nicolas Goaziou
uld not.
Define two LaTeX classes, one with "endfloat" package and one without.
Then use :EXPORT_LATEX_CLASS: node property.
Regards,
--
Nicolas Goaziou
dev/org-export-reference.html
Thanks for your interest in Org.
Regards,
--
Nicolas Goaziou
ault format string. Then we can
specify that "%d:%02d" is still available but should be deprecated.
It would also allow to skip months/weeks.
> +(defalias 'org-minutes-to-hh:mm-string 'org-minutes-to-clocksum-string)
> +(make-obsolete 'org-minutes-to-hh:mm-string 'org-minutes-to-clocksum-string
> +"org-mode version 7.9.3")
Good idea.
Regards,
--
Nicolas Goaziou
updated patch when I get time to make the changes.
Since it's for 8.0, there's no hurry. I'll wait for you to merge the two
patches and make subsequent changes.
Thank you.
Regards,
--
Nicolas Goaziou
ault-env "\\1{bmatrix}" table)))
"\n\\]")
(add-to-list 'org-export-filter-table-functions 'my-latex-table-to-matrix)
#+end_src
Regards,
--
Nicolas Goaziou
701 - 800 of 9824 matches
Mail list logo
