Am 25.02.2013 16:51, schrieb Sebastien Vauban:
Hi,
Suvayu Ali wrote:
On Fri, Feb 22, 2013 at 08:56:54PM +0100, Andreas Röhler wrote:
With exception of the noise, M-x report-emacs-bugs tends to send.
Org already uses one of its own: org-submit-bug-report
Maybe we could add an alias such as
`org-create-formula-image-with-imagemagick' doesn't handle the case that
`org-latex-pdf-process' is set to a function.
To reproduce:
- set `org-latex-pdf-process' to a function
- (setq org-latex-create-formula-image-program 'imagemagick)
this makes preview fail
- set #+OPTIONS: latex:image
Hi James,
Here is a third vote for mailcap. I have (only) this in my .mailcap
file:
application/pdf; okular '%s'; test=test -n "$DISPLAY"
It does the job.
Cheers,
Martin
PS Cool to see a (notorious) sc user on this list as well.
2013-13-25 08:06 James Harkins :
> On Feb 25, 2013 2:52 PM,
Sorry about the misinformation, wheezy current is using emacs 23.4 not
emacs 23.5.
On Mon, 25 Feb 2013, Michael Gauland wrote:
> Jude DaShiell shellworld.net> writes:
>
> > In toplevel form:
>
> > ox.el:80:1:Error: Cannot open load file: tabulated-list
>
> I ran into this as well, and resolv
Bastien writes:
> [1] http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=30d6dc
> [2] http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=662cb9
While your commits are rather small, I would likely never have figured
out how to do them, the magic goes over my head. It's a little like
playing go
Hi,
> Alternatives:
> I read about calfw and org2hpda. However, I did not found a way to generate a
> printable version of
> calfw (and I had trouble to set it up). For org2hpda I still struggle with
> the installation and it
> seems to be broken at the moment. Not sure.
I'm an author of calfw.
Nicolas Goaziou writes:
>> I have a problem where org-preview-latex-fragment appears not to use a
>> style file the latex header.
>>
>> Starting emacs like this:
>>
>> emacs -Q -l ~/minimal.el ~/file.org
>>
>> When I export the whole buffer to pdf it looks right.
>>
>> When I call org-preview-lat
Hey Seb,
On Mon, Feb 25, 2013 at 02:15:05PM +0100, Sebastien Vauban wrote:
>
> PS- By the way, there is already such a sort of template for Beamer...
I believe Nicolas' argument was, for the new exporter such a template
depends on the backend hence a default one for beamer makes sense but
not a
Dear Nicolas,
On 26.02.2013, at 00:14, Nicolas Goaziou wrote:
>> [...] This code used to be suppressed by
>>
>> :style-include-default nil
>> :style-include-scripts nil
>>
>> in the org-publish-project-alist - either this functionality is
>> currently not available or the keyword has changed. T
Just tested it, works now. Thanks! :D
On Mon, Feb 25, 2013 at 3:31 PM, Nicolas Goaziou wrote:
> Hello,
>
> Kyle Machulis writes:
>
> > I'm trying to html export my babel'd config. It seems to be choking on
> some
> > of the larger blocks (300+ lines) of code (offending blocks seem to be
> org,
>
Hello,
Kyle Machulis writes:
> I'm trying to html export my babel'd config. It seems to be choking on some
> of the larger blocks (300+ lines) of code (offending blocks seem to be org,
> erc, programming config). I should probably chop these down a bit for
> readability (still working on finshin
I'm trying to html export my babel'd config. It seems to be choking on some
of the larger blocks (300+ lines) of code (offending blocks seem to be org,
erc, programming config). I should probably chop these down a bit for
readability (still working on finshing org-ifying it), but I'd also figure
we
Hello,
Stefan Vollmar writes:
> if you look at the HTML code generated by Org-mode you will find this line in
> the embedded CSS code (line 45):
>
> div.figure p { text-align: center; }
>
> which causes the effect you have described.
> This code used to be suppressed by
>
> :style-include-def
Hello,
Myles English writes:
> I have a problem where org-preview-latex-fragment appears not to use a
> style file the latex header.
>
> Starting emacs like this:
>
> emacs -Q -l ~/minimal.el ~/file.org
>
> When I export the whole buffer to pdf it looks right.
>
> When I call org-preview-latex-f
Jonathan Leech-Pepin writes:
> For @xref{} I would need to know if it was at the start of a sentence and
> followed
> by a comma or period.
> For @pxref{} I would need to determine if it was at end of sentence,
> mid sentence followed by a comma or within parentheses, and not preceeded by
> "see
Dear Richard,
On 25.02.2013, at 18:55, Richard Stanton wrote:
> It seems that figure placement has changed in HTML files generated by the
> new (compared with the old) exporter.
>
> For example, here's a simple org file:
>
> -
>
> This is an org file
>
> [[file:figure.png]]
>
> * Abs
Hello
On 25 February 2013 16:48, Subhan Tindall wrote:
> I don't think there is a specific context that can clearly separate
> them. The differences are largely semantic, not syntactic. What is
> needed is some sort of marker on the tag in the original file telling
> it what kind of link is to b
Hello
On 25 February 2013 16:34, Subhan Tindall wrote:
> I noticed you left out @inforef, was that by design? It actually does
> behave quite differently than other members of the @*ref family, and
> the more arguments it gets the more different it looks IE Here's an
> example with a full 5 argu
Hi Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>>
>> It took me quite some time, but I'm at the end of converting a 90 slides
>> presentation from the old to the new exporter.
>>
>> In that presentation, there is (just!) one thing which does not work
>> anymore: the frame subtitle
Achim> D M German uvic.ca> writes:
>> I think the issue is that, at least in my computer the variable $\
>> returns empty (the record separator).
Achim> Thinko on my side, what I wanted was the input record separator "$/"
Achim> (to avoid
Achim> specifying a literal newline for those syst
Hello,
With recent versions of Org mode, the Highlighting of timestamps is not
happening between the right positions anymore: it begins one character before
the beginning of the timestamp, as you can see on
http://screencast.com/t/llxtNT3m.
Best regards,
Seb
--
Sebastien Vauban
I don't think there is a specific context that can clearly separate
them. The differences are largely semantic, not syntactic. What is
needed is some sort of marker on the tag in the original file telling
it what kind of link is to be used.
On Mon, Feb 25, 2013 at 1:38 PM, Nicolas Goaziou wrote
Hello,
Jonathan Leech-Pepin writes:
> I had to compare these possible outcomes when working on the texinfo
> exporter. Since links are parsed before being included in their
> paragraphs, I did not have a way to obtain context and therefore
> attempt to guess (and be successful) at which type of
I noticed you left out @inforef, was that by design? It actually does
behave quite differently than other members of the @*ref family, and
the more arguments it gets the more different it looks IE Here's an
example with a full 5 arguments:
REF *note Arg2: (Arg4)Lore Ipsum.
INFOREF *note Arg2: (Arg
Hi Tom,
wow, a daring project. This would indeed be a testimony to the quality of the
exporter if this works and gives proper output! I am curious and looking
forward to seeing the results.
- Carsten
On 25.2.2013, at 21:21, Thomas S. Dye wrote:
> Aloha all,
>
> An experiment to see if it
Jeffrey Brent McBeth writes:
> On Mon, Feb 25, 2013 at 10:48:16AM +0100, Bastien wrote:
>> Hi Tim,
>>
>> Tim Burt writes:
>>
>> > * lisp/org-datetree.el (org-datetree-find-year-create):
>> > Include regexp for tags. Syntax was taken directly
>> > from org-todo-line-tags-regexp in or
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> Hi all (and Nicolas),
>>
>> from =org-e-latex.el= (I have to upgrade - I know):
>> ,
>> | ;; Plain lists accept two optional attributes: `:environment' and
>> | ;; `:options'. The first one allows to use a non-stand
Nick Dokos wrote:
> Richard Stanton wrote:
>
> > I have org-export-html-postamble set to t. When I export a simple org
> > file that has no explicit #+date line (using the new exporter), I get a
> > line that says "Date:" at the bottom of the resulting HTML file, but
> > there's no date listed
Hello Nicolas,
Thanks for your prompt reply, though I think our discussion is a little
off-track here, as noted below.
Nicolas Goaziou writes:
> tftor...@tftorrey.com (T.F. Torrey) writes:
>
>>> It would be ATTR_HTML: :class "XXX". I try to unify syntax for
>>> attributes with syntax for Babel
(Here are the attached files, forgot to add them)
On 25 February 2013 15:24, Jonathan Leech-Pepin <
jonathan.leechpe...@gmail.com> wrote:
> Hello,
>
> On 25 February 2013 14:01, Subhan Tindall
> wrote:
>
>> The point being that compiling .texinfo source into an Info file
>> treats references dif
Hi,
I have been working on extending the KOMA letter support in Org. The
backend is still rough and I would like to more stuff such as
designing firstfood and firsthead with org elements (e.g. I use a
tabularx for my firstfood with varioues stuff).
I have changed the following objects:
1. Mak
Aloha all,
An experiment to see if it is possible to convert the Org manual to Org
is now (hopefully) at the "proof of concept" stage and I would like to
determine whether or not the approach is viable. The experiment is here:
https://github.com/tsdye/orgmanual.git
The file orgmanual.org has a h
Richard Stanton wrote:
> I have org-export-html-postamble set to t. When I export a simple org
> file that has no explicit #+date line (using the new exporter), I get a
> line that says "Date:" at the bottom of the resulting HTML file, but
> there's no date listed next to it. If I add an explici
Thomas Koch wrote:
> Hi,
>
> A common workflow (of mine) is: Work on something, submit and wait several
> days or weeks for a review or reply before I can continue. So I switch to the
> next task.
>
> I'd love if org-mode could keep track of tasks that are waiting for others
> and
> semi-au
Hi,
A common workflow (of mine) is: Work on something, submit and wait several
days or weeks for a review or reply before I can continue. So I switch to the
next task.
I'd love if org-mode could keep track of tasks that are waiting for others and
semi-automatically remind those others in a wee
Hello Bastien,
Bastien writes:
> hob...@poukram.net (Rémi Letot) writes:
>> So I get to ask if anyone that I'm not aware of is still currently
>> working on org-sync, and if yes if they are interrested in fixing the
>> redmine backend ?
>
> Daimrod is working on it and I think he is interested i
The point being that compiling .texinfo source into an Info file
treats references differently. For example:
(@pxref{my_node_name}). will compile just fine.
(@ref{my_node_name}). will not. There are also differences in case
(see v. See, note v. Note), and differences in output by ref type
dependi
Works.
My mistake.
Thanks for help.
Susan
Hello,
On 25 February 2013 13:40, Subhan Tindall wrote:
> There are 4 different ref commands, all with slightly syntactic
> requirements and outputs when compiled using makeinfo. I for one use
> @pxref{} a lot, and it has different requirements for placement than
> @ref or @xref (namely those tw
There are 4 different ref commands, all with slightly syntactic
requirements and outputs when compiled using makeinfo. I for one use
@pxref{} a lot, and it has different requirements for placement than
@ref or @xref (namely those two MUST have a . or , following the end
of the ref)
8.1 Different C
Hello Tom,
On 25 February 2013 12:52, Thomas S. Dye wrote:
> Aloha all,
>
> IIUC, there is currently no support for @pxref{} in the texinfo
> exporter. This is a texinfo @-command that does one thing in the info
> output and another in the LaTeX output.
>
Ultimately there is actually no real d
Hi Jon,
Jonathan Leech-Pepin writes:
> Hello Tom,
>
>> One nit: You have one space between the `::' at the end of a long title
>> and the start of the description, where the Org manual has two spaces.
>>
>>
> This should now be fixed (along with a logic error that was actually
> inserting
> desc
Susan Cragin wrote:
> Hi.
> I updated my emacs git, got the new org-mode, and tried M-S-UpArrow.
> And it worked. I was elated.
> And then I closed the program and re-opened it, and now it no longer works.
> The message is:
> This command is active in special context like tables, headlines or
I have org-export-html-postamble set to t. When I export a simple org
file that has no explicit #+date line (using the new exporter), I get a
line that says "Date:" at the bottom of the resulting HTML file, but
there's no date listed next to it. If I add an explicit #+date line, it is
correctly tr
Steinar Bang writes:
> But if I have this setting then notes created with `C-c C-z' end up on
> the top level, even if I manually create a :LOGBOOK: drawer.
>
> Is it possible to have both?
Unless it's been broken recently it should, but you probably need to
customize org-log-into-drawer to "t" (f
It seems that figure placement has changed in HTML files generated by the
new (compared with the old) exporter.
For example, here's a simple org file:
-
This is an org file
[[file:figure.png]]
* Abstract
This is an abstract
-
When I export, all looks fine, except that the fig
Aloha all,
IIUC, there is currently no support for @pxref{} in the texinfo
exporter. This is a texinfo @-command that does one thing in the info
output and another in the LaTeX output.
My idea is to create a custom link type, something like this:
(org-add-link-type
"pxref" nil
(lambda (
Hi.
I updated my emacs git, got the new org-mode, and tried M-S-UpArrow.
And it worked. I was elated.
And then I closed the program and re-opened it, and now it no longer works.
The message is:
This command is active in special context like tables, headlines or items
--Susan
Rainer M Krug writes:
> Well - I could and I guess nothing would change. Why I like my setup at the
> moment is, that I have
> all emacs config, installation and elpa in my .emacs.d directory. Would this
> be the same after
> using "make up2"? Would I have to change paths somewhere?
You can inst
Bastien writes:
> I fixed the comment, thanks.
I'm starting to sound like Drew, but the new comment says exactly what
the old one did, just the two parts juxtaposed.
The point of having the new macro is to avoid the question about
reverting the file when the file visited by a buffer has been edit
Hello Tom,
On 25 February 2013 11:57, Thomas S. Dye wrote:
> Hi Jon,
>
> Jonathan Leech-Pepin writes:
>
> > Hi Tom,
> >
> > On 21 February 2013 18:44, Thomas S. Dye wrote:
> >
> >> Hi Jon,
> >> [...]
> >>
> >> Based on this example from the Org manual, it looks as if the
> >> descriptions shou
Paul Sexton writes:
> I just never got around to fixing that minor glitch until now. I have
> committed a fix to the org-drill repository at
>
> http://bitbucket.org/eeeickythump/org-drill
>
> So if you download and use the org-drill.el from there, the problem
> will be fixed.
Thanks very much -
Hi Jon,
Jonathan Leech-Pepin writes:
> Hello,
>
> On 23 February 2013 18:04, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> [...]
>>
>> I eventually added :OPTIONAL_TITLE: property. Get its parsed value with
>> `org-export-get-optional-title' function.
>>
>> I patched ox-ascii, ox-latex and ox-html s
Hi Jon,
Jonathan Leech-Pepin writes:
> Hello Tom,
>
> I've now fixed this.
>
> Headlines with an :INDEX: property will now export as:
>
> #+BEGIN_EXAMPLE
> @unnumbered (or equivalent unnumbered subheading)
>
>
>
> @printindex (assuming INDEX is a recognized type, otherwise it
> will simply be
Hi Jon,
Jonathan Leech-Pepin writes:
> Hi Tom,
>
> On 21 February 2013 18:44, Thomas S. Dye wrote:
>
>> Hi Jon,
>> [...]
>>
>> Based on this example from the Org manual, it looks as if the
>> descriptions should start on column 32 or the third column after the end
>> of the title, whichever is
Hello,
"Sebastien Vauban"
writes:
> Hello Bastien,
>
> Bastien wrote:
>> Nicolas Goaziou writes:
>>
>>> It has been removed. Such a template depends on the back-end used, which
>>> was not the case of the previous implementation.
>>
>> One idea would be to have an equivalent of the now-defunc
Hi Paul,
Paul Sexton writes:
> So if you download and use the org-drill.el from there, the problem
> will be fixed.
Thanks for maintaining org-drill.el! I updated the version in the
contrib/ repository to org-drill.el 2.3.7.
Best,
--
Bastien
Nicolas Goaziou writes:
> this change because I was reinventing the wheel in
> `org-export-stack'. I hadn't realized [tabulated-list.el] was emacs24
> only. Bastien, is there another solution besides reverting the
> commit?
Could tabulated-list.el be conveyed within Org as org-tabulated-list.el
Hello Tom,
On 22 February 2013 18:28, Jonathan Leech-Pepin <
jonathan.leechpe...@gmail.com> wrote:
Hello Tom
On 22 February 2013 17:55, Thomas S. Dye wrote:
Aloha Jon,
[...]
I don't understand. This:
* Concept index
:PROPERTIES:
:TEXIN
Hello,
Jonathan Leech-Pepin writes:
> I've replaced the use of :TEXINFO_MENU_TITLE: with :OPTIONAL_TITLE:.
Thank you for looking into it.
Though, please use `org-export-get-optional-title' function instead.
OPTIONAL_TITLE property only contains the raw string. The function will
return the pars
Hello David,
On 19 February 2013 14:53, David Naumann wrote:
> I'm a happy, frequent user of org mode but there's something I can't
> figure out from the manual.
>
> What I would like to be able to do is insert a new heading at the same
> level as current, _following_ all the others. For exampl
"Sebastien Vauban"
writes:
>> [...] is new behavior as of the last couple of weeks.
>
> ... and I also experience a quite recent change.
>
> Before, when composing an email, I could edit lists and convert them
> from itemized to enumerated ones, such in:
>
> - blond -> 1. blond
> - brown
Hello
On 25 February 2013 11:09, Nicolas Goaziou wrote:
> Hello,
>
> Jonathan Leech-Pepin writes:
>
> > I've replaced the use of :TEXINFO_MENU_TITLE: with :OPTIONAL_TITLE:.
>
> Thank you for looking into it.
>
> Though, please use `org-export-get-optional-title' function instead.
> OPTIONAL_TIT
t...@tsdye.com (Thomas S. Dye) writes:
> In my case, the intended effects of `org-footnote-auto-adjust' were
> purely cosmetic in the Org buffer and didn't affect the output. Is
> there a situation where it does something that has an effect on
> output?
No, there is none.
> OK. Apologies for th
Hello,
Eric Schulte wrote:
> I use orgstruct mode in my message mode, so that I may easily include
> tables and lists when writing and responding to mail.
So do I...
> [...] is new behavior as of the last couple of weeks.
... and I also experience a quite recent change.
Before, when composing
Hello,
On 23 February 2013 18:04, Nicolas Goaziou wrote:
> Hello,
>
> [...]
>
> I eventually added :OPTIONAL_TITLE: property. Get its parsed value with
> `org-export-get-optional-title' function.
>
> I patched ox-ascii, ox-latex and ox-html so they use it when building
> a TOC. I think only ox-o
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I've learned that there are certain conditions (I don't know how many)
>> where the space after a sentence won't accept a footnote insertion.
>
> There shouldn't be any of such conditions.
Great. I'll be on the loo
Hi,
Suvayu Ali wrote:
> On Fri, Feb 22, 2013 at 08:56:54PM +0100, Andreas Röhler wrote:
>> With exception of the noise, M-x report-emacs-bugs tends to send.
>
> Org already uses one of its own: org-submit-bug-report
Maybe we could add an alias such as `M-x report-org-bugs' to mimick that one?
Be
Hi Tom,
On 21 February 2013 18:44, Thomas S. Dye wrote:
> Hi Jon,
> [...]
>
> Based on this example from the Org manual, it looks as if the
> descriptions should start on column 32 or the third column after the end
> of the title, whichever is greater.
>
>
I've just pushed a fix for this. It al
Hello Tom.
On 21 February 2013 18:26, Thomas S. Dye wrote:
> Hi Jon,
>
> Jonathan Leech-Pepin writes:
>
> > Hello Tom,
> >
> > On 21 February 2013 15:09, Thomas S. Dye wrote:
> >
> >> Aloha all,
> >>
> >> This link (which works correctly in the Org mode buffer):
> >>
> >> [[info:emacs#Indirect
Hello,
Bastien writes:
> Carsten Dominik writes:
>
>> I am curious why you chose the name "optional_title" for the
>> property? Why not, for example "TOC_TITLE" or something like this?
>
> I suggest EXPORT_ALT_TITLE instead.
>
> The EXPORT_ prefix seems more consistent with EXPORT_TITLE,
> and
Hello,
Thanks for extracting that patch from the other one.
Aaron Ecay writes:
> Tikz graphics should be exported to LaTeX by \include, not as a link.
> This commit changes the file extension used for tikz graphics from .tex
> to .tikz.
I'm wondering if it's really meant to be inserted as an in
Hello Bastien,
Bastien wrote:
> Nicolas Goaziou writes:
>
>> It has been removed. Such a template depends on the back-end used, which
>> was not the case of the previous implementation.
>
> One idea would be to have an equivalent of the now-defunct
> `org-insert-export-options-template' but for e
Hello,
François Pinard writes:
> This morning, I could not load Org because ox.el calls function
> tabulated-list, which does not seem to exist on this version of Emacs.
> So I fetched the one at https://github.com/sigma/tabulated-list.el to
> get going, but others will likely have the same prob
Hi, Org people.
This morning, I could not load Org because ox.el calls function
tabulated-list, which does not seem to exist on this version of Emacs.
So I fetched the one at https://github.com/sigma/tabulated-list.el to
get going, but others will likely have the same problem.
François
dmg writes:
> On Mon, Feb 25, 2013 at 1:54 AM, D M German wrote:
>>
>> Achim> You may misunderstand some things, or I don't understand what you are
>> Achim> asking. It is (at least currently) the responsibility of the Perl
>> Achim> program (or any other Babel language) to deliver the resul
On Mon, Feb 25, 2013 at 10:48:16AM +0100, Bastien wrote:
> Hi Tim,
>
> Tim Burt writes:
>
> > * lisp/org-datetree.el (org-datetree-find-year-create):
> > Include regexp for tags. Syntax was taken directly
> > from org-todo-line-tags-regexp in org.el.
>
> Applied, thanks a lot for t
Platform:
GNU Emacs 23.2.1 (i386-mingw-nt6.1.7600) of 2010-05-08 on G41R2F1
Org-mode version 7.9.1 (release_7.9.1-321-g9ebf47.dirty-git @
c:/Users/steinarb/Documents/git/org-mode/lisp/)
I have org-clock-into-drawer set to "CLOCK".
The idea is to put clocking info in the :CLOCK: drawer to avo
Hello,
Vincent Beffara writes:
>> #+ATTR_HTML: :options "width=\"400px\""
>>
>> This is heavier but will be consistent with other back-ends. Otherwise,
>> there is also:
>>
>> #+ATTR_HTML: :width "400px"
>>
>> But this requires to have a list of all properties supported.
>
> How about both? I
> #+ATTR_HTML: :options "width=\"400px\""
>
> This is heavier but will be consistent with other back-ends. Otherwise,
> there is also:
>
> #+ATTR_HTML: :width "400px"
>
> But this requires to have a list of all properties supported.
How about both? I.e. a short-list of common options (class, tit
tftor...@tftorrey.com (T.F. Torrey) writes:
>> It would be ATTR_HTML: :class "XXX". I try to unify syntax for
>> attributes with syntax for Babel and AFAICT, `html' is the last back-end
>> to have key="value" syntax.
>
> I see that this does not presently work, and the author listed on
> ox-html.e
Hi Daniel,
Daniel Hawthorne wrote:
> Greetings,
> After updating to 7.9.3e, I no longer am able to include a stylesheet
> link with the following syntax:
>
> #+STYLE: href="../relative/path/to/mystyle.css"/>
>
> If I go back to my previous version, it works as expected. It is not a path
> is
Until today, I had have these two (legacy) lines in my orgmode configuration
;; (global-font-lock-mode 1) ; for all buffers
which is already a default in emacs. This is also noted in the manual
http://orgmode.org/manual/Activation.html
However: it is still recommended in th
On Feb 25, 2013 2:52 PM, "Nick Dokos" wrote:
> I like putting things in ~/.mailcap, but you can season to taste.
Ok, that's 2 votes so far for mailcap. I'll try that later. Thanks!
hjh
By the way, `org-html-htmlized-org-css-url' docstring looks wrong.
`org-export-as-org' doesn't exist anymore, neither do "batch mode".
So, is the variable still useful? If it is, could someone could fix its
docstring so it reflects what is really happening?
Thank you.
Regards,
--
Nicolas Goaz
D M German uvic.ca> writes:
> I think the issue is that, at least in my computer the variable $\
> returns empty (the record separator).
Thinko on my side, what I wanted was the input record separator "$/" (to avoid
specifying a literal newline for those systems where this is actually
multi-char
Hello,
Rick Frankel writes:
> * lisp/ox-html.el:
> (org-export-define-backend): add css url option
> (org-export-htmlized-org-css-url): modify docstring and options.
> (org-html--build-style): include css-url if specified.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Hi,
The attached is the new version of org-mew.el with several new features.
I would appreciate it if some of Mew users could try this.
If this is fine, I would like Bastien to incorporate it to the git repo.
The changes are as follows:
org-mew-store-link
- Works in mew message mode as well as
Hi,
still trying to get a printed calendar including all org-agendas, I noticed
that the calendar/diary built-in function in emacs allows export of
calendar views.
Guess that and some post-processing for the print-job is all I need.
However, I did not find a way how-to add org-agenda entries into
Hello Nicolas,
Nicolas Goaziou writes:
> tftor...@tftorrey.com (T.F. Torrey) writes:
>
>>> You don't assign attributes to an image in a paragraph, you assign
>>> attributes to the paragraph itself.
>>
>> It would be nice if there actually was a way to assign an attribute to a
>> paragraph, so th
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> In the document I'm editing, I have sentences like this:
>
> If you want a list to start with a different value (e.g., 20),[fn:17]
> start the text of the item with ~[@20]~.
>
> As a matter of style, I prefer the footnote (which contains qualify
Hi Achim,
Achim Gratz writes:
> We shouldn't define things that don't have an org prefix.
Fair enough.
(Note that `with-buffer-modified-unmodified', from which
org-unmodified was heavily copied, lives in bookmark.el. Perhaps
Emacs should put it elsewhere.)
> I don't really see why we needed
On 25 feb. 2013, at 10:28, Bastien wrote:
> Hi François,
>
> sorting list items and headlines is now done against the visible
> part of the item and headlines, i.e., it ignores hidden links and
> emphasis markers.
Hi Bastien,
are you sure it removes emphasis markers as well? Looks to me that
Hi Carsten,
Carsten Dominik writes:
> are you sure it removes emphasis markers as well? Looks to me that
> org-sort-remove-invisible only removes links. I guess it could be
> rewritten looking at invisibility properties, but that might be problematic
> when sorting includes a part of the buffe
Rainer M Krug writes:
> Quick follow up question - what is the value for the Ubuntu package?
I'm not using Ubuntu so I don't know, sorry!
--
Bastien
Nicolas Goaziou writes:
> Hello,
>
> henry atting writes:
>
>> Since the last pull (release_7.9.3f-1205-g0030e1) headlines are exported
>> to LaTeX like this:
>>
>> \subsection*[Headline]{Headline}
>>
>> which does not produce proper headlines in the resulting pdf.
>
> It should be fixed now. Th
Carsten Dominik writes:
> On 25 feb. 2013, at 10:10, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> Eric Abrahamsen writes:
>>
>>> Calling `org-fill-paragraph' inside a table leaves point at the end of
>>> the table, for reasons that are totally unclear to me.
>>>
>>> I've tested this with up-to-d
Hello,
henry atting writes:
> Since the last pull (release_7.9.3f-1205-g0030e1) headlines are exported
> to LaTeX like this:
>
> \subsection*[Headline]{Headline}
>
> which does not produce proper headlines in the resulting pdf.
It should be fixed now. Thank you.
Regards,
--
Nicolas Goaziou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/02/13 22:17, Achim Gratz wrote:
> Rainer M Krug writes:
>> Ok - that makes sense. I just checked in my contrib/lisp and I only have .el
>> there, so none
>> are compiled.
>
> Look in lisp, not contrib/lisp.
True - because it compiles it there.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/02/13 16:42, Achim Gratz wrote:
> Bastien altern.org> writes:
>>> Just for clarifications: is there any problem with adding
>>>
>>> ORG_ADD_CONTRIB = *
>>>
>>> to the local.mk file, apart from slightly longer compilation times?
>>
>> This sho
1 - 100 of 119 matches
Mail list logo
