Re: [O] Thanks for Lilypond export (and minor comments)
Hi Eric, Eric Schulte schulte.e...@gmail.com writes: Thanks for finding this error Torsten! I've just pushed up a fix. Thanks. Bastien, is there a process for bug-fix commits like this one which should be pushed through to Emacs24? I'm thinking a branch (maintenance?) to which this should be pushed or a special way to tag the commit? there is none for now -- I need to think about it. As I will need a few hours more to create the ChangeLog between 7.5 and 7.6 for Emacs (yeah!), I plan to make a minor release 7.6.1 that will be the one we'll have in Emacs. Probably tomorrow morning or sunday morning. So this fix will go thru Emacs, then we can think about a better process. Detailed suggestions from git power users welcome! Thanks, -- Bastien
Re: [O] Bug: OrgMobile errors on push with custom functions in the agenda dispatcher [7.5 (release_7.5.580.g301b34)]
Hi Tassilo, Here's a patch that fixes the issue. Applied, thanks! -- Bastien
Re: [O] LaTex export: How to use `csquotes' and `\enquote{}'
Thomas S. Dye t...@tsdye.com wrote:
Hi Nick,
Nick Dokos nicholas.do...@hp.com writes:
Thomas S. Dye t...@tsdye.com wrote:
Hi Nick,
Good point.
How about three new variables, org-export-latex-open-double-quotes,
org-export-latex-close-double-quotes, and org-export-latex-single-quote?
The regexp stuff could stay as hard code and the user would only be able
to mess up what actually ends up being exported.
That's a pretty good idea: simple implementation, no extra options,
set-and-forget
and it only affects the latex exporter.
Tom, you win the jackpot: you'll have the patch ready by tomorrow?
Nick
I think we're still a bit short of the jackpot, or at least I am. I
don't understand why (equal lang fr) requires a different regexp in
the first list. Do you?
Is the different regexp needed for fr text when using csquotes? Or is
this difference handled by csquotes, too?
I believe it is just a hack - I mentioned it in an earlier post and I think
it can safely go away: csquotes will take care of it very nicely.
That said, tomorrow is a congenial deadline, so long as you're willing
to stick to it for the next few days, at least.
Sounds good: there's always tomorrow. BTW, since you are doing the hard
work here, I'll volunteer to write a section for the LaTeX tutorial (but
if you prefer to write it, I will defer).
Nick
All the best,
Tom
All the best,
Tom
=20
Nick Dokos nicholas.do...@hp.com writes:
Responses to Frederik and Tom inline.
Frederik freak.f...@gmail.com writes:
Why not use one option for babel and another for csquotes? I thought
of something like this:
#+OPTIONS: babel:english,ngerman csquotes:autostyle,german=3Dguillemets
I did suggest different options, one controlling babel and the other
controlling csquotes. The problem with the above is that it is very
LaTeX-specific: the options and their values have no meaning outside of
that. I think that we should strive to use more generic options that
would at least be usable by other export engines.
Or is there any other reason why one would like to specify language
opti=
ons?
Sadly I don't have the skills to suggest a patch...
I definitely see Nick's point: simplicity is one of the most important
features of org-mode. So a possible decision not to support csquotes
is absolutely understandable.
I'll be very surprised if there is no support for csquotes within a
couple
of weeks (maybe within a couple of days :-) ) The question is what form
will it take?
Thomas S. Dye t...@tsdye.com wrote:
I'm wondering if a simpler solution than Nick's might be to replace the
lists at the end of this code snippet with a variable, say
org-export-latex-quote-mechanism. Initially, the variable would be set
to the second list. If the user wanted something different, then the
user would be responsible for setting the variable to the different
quoting mechanism, whether it be \enquote{ or something else. The user
would also be responsible for making sure the LaTeX packages needed to
support the quoting mechanism were loaded and functional.
=20
(defun org-export-latex-quotation-marks ()
Export quotation marks depending on language conventions.
(let* ((lang (plist-get org-export-latex-options-plist :language))
(quote-rpl (if (equal lang fr)
'((\\(\\s-\\)\ =C2=AB~)
(\\(\\S-\\)\ ~=C2=BB)
(\\(\\s-\\)' `))
'((\\(\\s-\\|[[(]\\)\ ``)
(\\(\\S-\\)\ '')
(\\(\\s-\\|(\\)' `)
=20
This might provide Org-mode the flexibility needed to support csquotes,
but also leave open the possibility of supporting other packages, as
well.
=20
Maybe - this is the kind of mechanism that is used for
org-export-latex-classes for example, so there is definitely
precedent. OTOH, the lists above look like hen scratchings (or line
noise if you prefer, or -- I'll get in trouble for this -- Perl
code :-)), so it would be easy to get things wrong if you have to
cut-and-paste-and-edit which I think one would have to do to customize
it: it's OK to expect *one* developer to get it right, but it's not
OK to expect 100 users to get it right.
So it might be simpler to implement, but I'm not sure it might be
simpler to use. I've supported using existing mechanisms to implement
new behavior before and not disturbing the existing structure too much
(e.g. the revtex stuff that Sebastian Hoffert was (is?) working on).
But if it leads to e.g. an implementation that befuddles users, then
you end up with a flood of questions on the ML. So it's a balancing
act.
BTW, you mention the possibility of supporting other packages. I didn't
find anything useful in
Re: [O] Thanks for Lilypond export (and minor comments)
Bastien b...@altern.org wrote: is there a process for bug-fix commits like this one which should be pushed through to Emacs24? I'm thinking a branch (maintenance?) to which this should be pushed or a special way to tag the commit? there is none for now -- I need to think about it. As I will need a few hours more to create the ChangeLog between 7.5 and 7.6 for Emacs (yeah!), I plan to make a minor release 7.6.1 that will be the one we'll have in Emacs. Probably tomorrow morning or sunday morning. So this fix will go thru Emacs, then we can think about a better process. Detailed suggestions from git power users welcome! I'm not sure whether I posted this before but if you haven't seen it before, it's probably worth reading: http://nvie.com/posts/a-successful-git-branching-model/ There is a set of tools that supports this kind of workflow at https://github.com/nvie/gitflow Nick
Re: [O] LaTex export: How to use `csquotes' and `\enquote{}'
Hi Nick and Tom, Nick Dokos nicholas.do...@hp.com writes: Sounds good: there's always tomorrow. BTW, since you are doing the hard work here, I'll volunteer to write a section for the LaTeX tutorial (but if you prefer to write it, I will defer). I'm following this thread and waiting for the patch -- would be nice to apply it before 7.6.1 (this WE), which will go to Emacs. Good luck! -- Bastien
Re: [O] HTML Postamble is inside Content DIV
Hi Pierre, Any objection for applying this patch? Pierre de Buyl wrote: I checked and indeed content is working well. Pierre Le 1 juil. 11 à 16:06, Sebastien Vauban a écrit : Hi Pierre, Pierre de Buyl wrote: Le 28 juin 11 à 23:45, Sebastien Vauban a écrit : Here is thus my proposition for a better div-structured HTML. There are only four parts required in the HTML for all the magic to work with the CSS: - The first part is a container div (content, by default) that surrounds everything. - Inside that are three more parts: + a preamble (in a div, if the user wants it), + a div body and + a postamble (in a div, if the user wants it). I think my regular use of the html export would be broken. We'll try to solve that, then. I add a div id=wrapper in the preamble and a /div in the postamble. This allows me to make a boxed page (see http://homepages.ulb.ac.be/~pdebuyl/ ) which I like. If I cannot end my div in the postamble, I think it would break my setup. Here is my setup: :html-preamble div id=\wrapper\ div id=\menu\ HERE, some static menu items. /div :html-postamble /div Why are you adding a `wrapper' div in the already existing `content' div (that surrounds everything). I see no real difference between both. I tried without that extra div and I cannot reproduce my former layout. Would you apply your CSS rule onto `content', would that make a diff? Best regards, Seb -- Sebastien Vauban
Re: [O] patch org-mode Makefile - solve a couple debian build problems and a slackware build problem
No I can't provide any patch that works with all distros. I don't have all distros available to me; not all Linux distros are accessible for screen reader users either. I use screen reading software just to use a computer and I don't have all distros even under the category of distros that are accessible yet. To use org-mode default uncomment /usr/local as prefix for all systems that put emacs stuff or some emacs stuff under /usr/local. For Slackware and Debian though, /usr/local isn't in the load-paths. The install-info part of the patch was using debian's install-info program all along and that was apparently depricated in favor of ginstall-info. That change will effect other distros into the future as they update their packages. The org-mode default would be to uncomment install-info choice but debian squeeze needs ginstall-info uncommented. There's another reason I can't provide better patches. The Makefile structure itself. I wrote code earlier which tested if [ -r /etc/debian_version ]; then and took action if that was true but putting it into the variables section of the Make file and running make caused make to freak out on me with the complaint that commands were in the variables section. Apparently Makefile structure and COBOL share some similarities and not the good ones. On Thu, 7 Jul 2011, Bastien wrote: Hi Jude, I infer this patch will break most non-debian/slackware configs. Could you provide a patch that works for *every* distro, including debian and slackware? Thanks! Jude DaShiell jdash...@shellworld.net writes: diff -c a//Makefile b//Makefile *** a//Makefile 2011-07-05 21:05:08.0 -0400 --- b//Makefile 2011-07-05 21:05:21.0 -0400
Re: [O] Thanks for Lilypond export (and minor comments)
Hi I first had to load dot support (because you are calling org-babel-expand-body:dot). If you want to also attract musicians (without Thanks for finding this error Torsten! I've just pushed up a fix. Thanks Torsten for the heads-up, and thanks Eric for the rapid response. Regards Martyn
Re: [O] working with delimited files
Hi Sivaram, Sivaram Neelakantan nsivaram@gmail.com writes: This makes it easier to read as you can see below | BEL | EQ | 02-Jan-2006 | 993.15 | 998 |1001 | 983 |.. | BEL | EQ | 03-Jan-2006 | 989.05 | 999.5 |1000 | 989.9 |.. | BEL | EQ | 04-Jan-2006 | 994.35 | 998 |1014 | 986.15 |.. How do I use the overlay for editing but keep the underlying file structure? I can see a solution where you could add an overlay to display the table (say, with C-u C-c |, for example) but you won't be able to *edit*. Would that be something you (and others) would find useful? -- Bastien
Re: [O] Syntax for tags-todo in org-agenda-custom-commands
Hi Loris, Loris Bennett loris.benn...@fu-berlin.de writes: In my org-agenda-custom-commands I've got two block entries: tags-todo office(project|task) and tags-todo home(project|task) Items with :office:project: and :home:project: are separated properly, but :office:task: and :home:task: end up in both lists. Can you send a test file, with actual results and expected results? I _guess_ the problem you have, but I'd like to see/test it. What should the correct syntax be and where is it described? Did you look in the manual? What is missing? Thanks! -- Bastien
Re: [O] working with delimited files
On Fri, Jul 8, 2011 at 10:12 AM, Bastien b...@altern.org wrote: Hi Sivaram, Sivaram Neelakantan nsivaram@gmail.com writes: This makes it easier to read as you can see below | BEL | EQ | 02-Jan-2006 | 993.15 | 998 |1001 | 983 |.. | BEL | EQ | 03-Jan-2006 | 989.05 | 999.5 |1000 | 989.9 |.. | BEL | EQ | 04-Jan-2006 | 994.35 | 998 |1014 | 986.15 |.. How do I use the overlay for editing but keep the underlying file structure? I can see a solution where you could add an overlay to display the table (say, with C-u C-c |, for example) but you won't be able to *edit*. Would that be something you (and others) would find useful? Definitely useful - a read-only viewer of delimited files, would be a useful feature (and sometimes safer then an editor) which I would use regularly. But a really nice feature would be to be able to open a delimited file as a table, then being able to edit it using all the usual org features for tables, and being able to export the table to the delimited format again, while at the same time being able to save the org file. So there would be two aspects: 1) import delimited file into org-table 2) export of table into delimited format Both in itself would be very useful, but together they would be brilliant. Rainer -- Bastien -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax (F): +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug
Re: [O] patch org-mode Makefile - solve a couple debian build problems and a slackware build problem
Hi Jude, I understand. I think we can go with a FAQ: How to compile and install Org under Debian and Slackware?, then include your patch in the answer. Can someone confirm Jude's patch solves install issues for Debian and Slackware? Thanks, -- Bastien
Re: [O] how to refer row's by name in a spreadsheet formula?
Hi Jiang, jiangzuo...@gmail.com jiangzuo...@gmail.com writes: Formulas reference in a long table are very easy corrupted by manually inserting. so, I think, refer using name instead of num. is better. but how to refer the rows by name? For example, |---+--+-++-+--| | ! | date | amount | item | account | note | | | date | amount | item | account | note | |---+--+-++-+--| | _ | | bamount | | | | | | | 12 | lunch | pocket | | | | | 59 | dinner | pocket | | | ^ | | eamount | | | | |---+--+-++-+--| | _ | | total | | | | | # | | #ERROR | | | | |---+--+-++-+--| #+TBLFM: $total=vsum($bamount..$eamount);%.2f I'd expected $bamount..$eamount is the range of @II$amount..@III$amount, but it's not. $bamount and $eamount are epxanded to the values too early. I see the problem you have. To my understanding, field names like bamount and eamount refer to the _value_ of the above/below field, not to the _position_. So when the formula is computed, these names are replaced by values, not by position -- hence the result you have. I'm not sure this is by design. Maybe Carsten can tell more, and/or have a look in this issue when he's back. Best, -- Bastien
Re: [O] Calendar-like view of the org-agenda
Hi Manuel, Manuel Hermenegildo he...@fi.upm.es writes: I.e., an idea would be to add a back end to the code that generates the org agenda which, instead of rendering the agenda creates the calfw objects. I'm all for an Org agenda backend -- but before that, we *need* to make `org-agenda-get-day-entries' much more efficient. If someone manages to reduce the execution time of this function by 20%, then I'll work on such a backend :) The challenge is open -- no deadline! -- Bastien
Re: [O] Babel: 1st version for music notation language Fomus
Dear Eric, On 8 Jul 2011, at 02:38, Eric Schulte wrote: Thanks for sharing this, it looks great, short clear and to the point. Shall I add it to the contrib/ directory? If you think it is already at that point, that is certainly fine by me. Best, Torsten Best -- Eric Torsten Anders torsten.and...@beds.ac.uk writes: Dear Babel developers, Inspired by the newly available Lilypond, I hacked up a first version of language support for Fomus (http://fomus.sourceforge.net/). Briefly, Fomus is a music notation system that translates a relatively simple domain specific music language into multiple output formats, including Lilypond and MusicXML (the latter is an open format supported by many commercial music notation systems such as Finale and Sibelius). In a nutshell, Fomus can simplify the generation of complex scores, because it can add various score information automatically. Anyway, please find my first attempt of a Fomus integration attached. This works already fine for standard code blocks such as the following. Note that the result of this is a Lilypond file. #+begin_src fomus :file test1.ly time 0 dur 2 pitch 60; time 2 dur 1 pitch 62; time 3 dur 1 pitch 63; time 4 dur 4 pitch 65; #+end_src Of course, because this is a quick hack, various improvements can be made. For example, it might be a good idea to allow for something like :file test.pdf, where the resulting Lilypond call would see file.ly, but the automatically inserted link in the org buffer would be the resulting file.pdf. Comments are welcome. Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://strasheela.sourceforge.net http://www.torsten-anders.de -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel] feature request: extracting non-sequential columns and/or rows from a table
Eric Schulte schulte.e...@gmail.com writes: Hi Eric, Unfortunately I recently became very busy, so I will not be able to address this any time soon. Hi Eric. That's perfectly fine! I completely understand. As I said, it's a very low priority request. However, the indexing behavior is self contained in the `org-babel-ref-index-list' function, so feel free to take a crack at that function. If you are able to implement your syntax as described below I would be happy to help fold in the change. I will do so, i.e. attempt it, but don't hold your breath ;-) my elisp capabilities may not be up to it but it sounds like a good project for the summer... thanks, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.6 (release_7.6.4.gf305a)
Re: [O] Thanks for Lilypond export (and minor comments)
Hi Nick, Nick Dokos nicholas.do...@hp.com writes: I'm not sure whether I posted this before but if you haven't seen it before, it's probably worth reading: http://nvie.com/posts/a-successful-git-branching-model/ Nice read -- thanks. In fact, we *do* have a documented process for important fixes that need to go to the maint branch. See README_maintainer: ,[ Minor releases ] | The release number for minor releases look like this: =7.13.01= | | Minor releases are small amends to main releases. Usually they fix | critical bugs discovered in a main release. Minor bugs are not | fixed - they will be adressed in the next main release. Only the fix | to the bug is bundled into a release, without the main development | work going on in the master branch. Since the bug fix will also be | needed in the master branch, usually the fix is made in master and | then cherry-picked into maint. When this is done, a release is made | from maint with this command: | | : make fixrelease TAG=7.13.01 ` So in the case Eric raised, I would ideally cherry-pick important fixes from the master branch to the maint branch then make a release based on this maint branch. I think this makes sense when the master (development) branch is quite unstable, with several untested features. As long that I'm confident many testers use the latest master branch, I'm reluctant to go through the hassle of cherry-picking commits... and just release a minor release with all latest dev from master. Call me lazy, but I'd rather keeping things simple here. -- Bastien
Re: [O] org and microsoft exchange
Matthieu Lemerre ra...@free.fr writes: I have no idea what I will need to do! I really am truly ignorant of the whole MS world other than I know, if push comes to shove, I can install cygwin and then Emacs when I have to... ;-) Actually, there are emacs binaries for win32 that work without needing cygwin. thanks; but cygwin seems natural to install in conjunction with emacs as I want bash et al. if I ever have to use Windows. having said this, it's been years since I have had to do this luckily (for me). For the record, here are some other things that I tried/maybe worth trying: - Davmail + thunderbird: allows accessing exchange mail and calendar and syncinc with it, but did not manage to import org ics into that. - Evolution and the openexchange client may be other things to try. These two seem to imply using something other than Emacs for my email? Or have I misunderstood? Openexchange is a command line tool to synchronize with an exchange server. But it is still incomplete, and I found it a nightmare to configure and use. Evolution is indeed another mail client, but my intent was to use it solely as a mean to synchronize the org mode ics file with the exchange calendar. Instead of using outlook for this... Thanks for the explanation. -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.6 (release_7.6.4.gf305a)
Re: [O] patch org-mode Makefile - solve a couple debian build problems and a slackware build problem
Jude DaShiell jdash...@shellworld.net wrote:
To use org-mode default uncomment /usr/local as prefix for all systems
that put emacs stuff or some emacs stuff under /usr/local. For
Slackware and Debian though, /usr/local isn't in the load-paths. The
install-info part of the patch was using debian's install-info program
all along and that was apparently depricated in favor of ginstall-info.
That change will effect other distros into the future as they update
their packages. The org-mode default would be to uncomment install-info
choice but debian squeeze needs ginstall-info uncommented. There's
another reason I can't provide better patches. The Makefile structure
itself. I wrote code earlier which tested if [ -r /etc/debian_version
]; then and took action if that was true but putting it into the
variables section of the Make file and running make caused make to freak
out on me with the complaint that commands were in the variables
section. Apparently Makefile structure and COBOL share some
similarities and not the good ones.
Most Linux systems I know of have a description of what distro is
installed in the /etc/issue file: Ubuntu, Debian, RH, Fedora, SuSE
certainly have it and others might (but I haven't run Slackware in 10
years, so I don't know if that's the case on it). If /etc/issue exists
and contains what I think it contains, then GNU make will parse a
Makefile like this:
--8---cut here---start-8---
distro = $(shell sed 1q /etc/issue | cut -d' ' -f1 | tr A-Z a-z)
# default values
path=/usr/local
installinfo=install-info
ifeq ($(distro),debian)
path=/usr/deb
installinfo=ginstall-info
endif
ifeq ($(distro),slackware)
path=/usr/slack
endif
all:
echo ${path}
echo ${installinfo}
--8---cut here---end---8---
There are supposedly better ways to write the conditionals, but trying
them on recent Ubuntu and old Debian, I got inconsistent results, so
I fell back to the above in order to satisfy both. I believe that
(modulo the existence of /etc/issue) it should run on any Linux distro
of any (relatively recent: say the last five years) vintage.
Having said that, I'm not sure that Jude's diagnosis is completely
correct. It might very well be the case that debian squeeze installs
ginstall-info only: they certainly did that with earlier versions. On
my Ubuntu 10.04 laptop, I have both and they are *different* programs:
-rwxr-xr-x 1 root root 40512 2010-02-11 08:49 /usr/bin/ginstall-info
-rwxr-xr-x 1 root root 6216 2011-01-06 14:15 /usr/sbin/install-info
In fact, on Ubuntu, install-info is a wrapper around ginstall-info:
in normal usage, it does not do *anything* other than calling ginstall-info.
Read the manual page for more details.
On debian, the problem can be circumvented by planting a symlink
wherever ginstall-info is installed:
sudo ln -s /usr/bin/ginstall-info /usr/bin/install-info
Or the makefile can figure out if install-info exists and if it does not,
use ginstall-info in a way similar to the above:
--8---cut here---start-8---
iiprog = $(shell which install-info)
# check if it is empty
ifeq ($(strip $(iiprog)),)
iiprog = ginstall-info
endif
--8---cut here---end---8---
What I don't understand is the load-path comment: what is it that is
stopping one from adding /usr/local/something/or/other to his/her load-path and
putting
it in the appropriate place in the list? Same thing with
Info-directory-list. I like to initialize the latter from the INFOPATH
environment variable, but in any case it ends up like this:
,
| Info-directory-list is a variable defined in `info.el'.
| Its value is
| (/home/nick/src/emacs/org/org-mode/doc /usr/local/share/info
/usr/share/info)
`
Isn't that enough?
Do other users of debian and slackware have similar difficulties? If so, why?
Nick
PS and then there is OS X and Windows, and other Unixes and who knows what
else...
On Thu, 7 Jul 2011, Bastien wrote:
Hi Jude,
I infer this patch will break most non-debian/slackware configs.
Could you provide a patch that works for *every* distro, including
debian and slackware?
Thanks!
Jude DaShiell jdash...@shellworld.net writes:
diff -c a//Makefile b//Makefile
*** a//Makefile 2011-07-05 21:05:08.0 -0400
--- b//Makefile 2011-07-05 21:05:21.0 -0400
Re: [O] patch org-mode Makefile - solve a couple debian build problems and a slackware build problem
Hi Nick, Nick Dokos nicholas.do...@hp.com writes: PS and then there is OS X and Windows, and other Unixes and who knows what else... Indeed. I'll apply every patch that - doesn't break current Makefile commands - does add a new func (even tiny) for specific distro Please send some :) -- Bastien
Re: [O] HTML Postamble is inside Content DIV
Not at all. Pierre Le 8 juil. 11 à 09:36, Sebastien Vauban a écrit : Hi Pierre, Any objection for applying this patch? Pierre de Buyl wrote: I checked and indeed content is working well. Pierre Le 1 juil. 11 à 16:06, Sebastien Vauban a écrit : Hi Pierre, Pierre de Buyl wrote: Le 28 juin 11 à 23:45, Sebastien Vauban a écrit : Here is thus my proposition for a better div-structured HTML. There are only four parts required in the HTML for all the magic to work with the CSS: - The first part is a container div (content, by default) that surrounds everything. - Inside that are three more parts: + a preamble (in a div, if the user wants it), + a div body and + a postamble (in a div, if the user wants it). I think my regular use of the html export would be broken. We'll try to solve that, then. I add a div id=wrapper in the preamble and a /div in the postamble. This allows me to make a boxed page (see http://homepages.ulb.ac.be/~pdebuyl/ ) which I like. If I cannot end my div in the postamble, I think it would break my setup. Here is my setup: :html-preamble div id=\wrapper\ div id=\menu\ HERE, some static menu items. /div :html-postamble /div Why are you adding a `wrapper' div in the already existing `content' div (that surrounds everything). I see no real difference between both. I tried without that extra div and I cannot reproduce my former layout. Would you apply your CSS rule onto `content', would that make a diff? Best regards, Seb -- Sebastien Vauban
Re: [O] Calendar-like view of the org-agenda
Hi Masashi, SAKURAI Masashi m.saku...@kiwanami.net writes: the re-design of the whole org-agenda-list algorithm seems to be needed, because the key function org-agenda-get-day-entries requires only one date and the subsequent dependent functions also are designed by the API. FWIW, I'm all ears -- if you have ideas on how to make org-agenda-list more effective please let us know, I could try to implement them. Best, -- Bastien
Re: [O] org and microsoft exchange
Hi Matthieu, Matthieu Lemerre ra...@free.fr writes: Compared to what org-mode currently exports, only three fields are missing: - Organizer. This should not be too hard to do (using user-mail-adress). Okay. - Method:request (should also be easy...) Should this field be present in every entry? What does it mean? - The sequence number is more difficult. I think it could be stored as a property of an org-mode node, but when should it be updated? Maybe it can be just be updated everytime the file is exported, just as ids are created when the file is exported. What means the SEQUENCE field? Thanks for further information! -- Bastien
Re: [O] patch org-mode Makefile - solve a couple debian build problems and a slackware build problem
Jude DaShiell jdash...@shellworld.net writes: No I can't provide any patch that works with all distros. I don't have all distros available to me; not all Linux distros are accessible for screen reader users either. I use screen reading software just to use a computer and I don't have all distros even under the category of distros that are accessible yet. I think there are build services that can simulate different architectures and (maybe) distros. I wonder whether SuSE's build farm could help you out here. https://build.opensuse.org/ I am sure there are hosted services out there particularly to cater to this need. You only need to talk to some folks who do packaging and they will be able to point you to or lend some machine in the cloud that you can use for deployment. Why bother about Makefile etc for installing. Just use Emacs package-manager for installing. M-x list-packages. You need Emacs-24.? though. I am sure you can take your initiative a step further and send a feeler to folks in the distros mailing list. To use org-mode default uncomment /usr/local as prefix for all systems that put emacs stuff or some emacs stuff under /usr/local. For Slackware and Debian though, /usr/local isn't in the load-paths. The install-info part of the patch was using debian's install-info program all along and that was apparently depricated in favor of ginstall-info. That change will effect other distros into the future as they update their packages. The org-mode default would be to uncomment install-info choice but debian squeeze needs ginstall-info uncommented. There's another reason I can't provide better patches. The Makefile structure itself. I wrote code earlier which tested if [ -r /etc/debian_version ]; then and took action if that was true but putting it into the variables section of the Make file and running make caused make to freak out on me with the complaint that commands were in the variables section. Apparently Makefile structure and COBOL share some similarities and not the good ones. On Thu, 7 Jul 2011, Bastien wrote: Hi Jude, I infer this patch will break most non-debian/slackware configs. Could you provide a patch that works for *every* distro, including debian and slackware? Thanks! Jude DaShiell jdash...@shellworld.net writes: diff -c a//Makefile b//Makefile *** a//Makefile2011-07-05 21:05:08.0 -0400 --- b//Makefile2011-07-05 21:05:21.0 -0400 --
Re: [O] working with delimited files
On Fri, Jul 08 2011,Rainer M Krug Rainer M Krug wrote:
[snipped 20 lines]
Definitely useful - a read-only viewer of delimited files, would be a
useful feature (and sometimes safer then an editor) which I would use
regularly.
But a really nice feature would be to be able to open a delimited file as a
table, then being able to edit it using all the usual org features for
tables, and being able to export the table to the delimited format again,
while at the same time being able to save the org file. So there would be
two aspects:
1) import delimited file into org-table
2) export of table into delimited format
Both in itself would be very useful, but together they would be brilliant.
Exactly! And auto-{number/name}ing of the columns when importing would
also be nice.
[snipped 10 lines]
sivaram
--
Re: [O] Syntax for tags-todo in org-agenda-custom-commands
Hi Bastien, Bastien b...@altern.org writes: Hi Loris, Loris Bennett loris.benn...@fu-berlin.de writes: In my org-agenda-custom-commands I've got two block entries: tags-todo office(project|task) and tags-todo home(project|task) Items with :office:project: and :home:project: are separated properly, but :office:task: and :home:task: end up in both lists. Can you send a test file, with actual results and expected results? Test file: * Tasks :task: ** TODO Mow lawn:home: ** TODO Install R :office: * Projects :project: ** TODO Set up cluster:office: ** TODO Sort out backup :home: Actual Results: Office agendatest: TODO Mow lawn :task::home: agendatest: TODO Install R :task::office: agendatest: TODO Set up cluster :project::office: Home TODOs agendatest: TODO Mow lawn :task::home: agendatest: TODO Install R :task::office: agendatest: TODO Sort out backup :project::home: Expected Results: Office agendatest: TODO Install R :task::office: agendatest: TODO Set up cluster :project::office: Home TODOs agendatest: TODO Mow lawn :task::home: agendatest: TODO Sort out backup :project::home: I hope this is complete. I don't quite know what the best way to test something like this is without disturbing my configuration too much. I _guess_ the problem you have, but I'd like to see/test it. What should the correct syntax be and where is it described? Did you look in the manual? What is missing? I looked here http://orgmode.org/manual/Block-agenda.html#Block-agenda but there is no complex example with and-ing and or-ing tags. Thanks! Thank you for taking the time. Cheers Loris -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email loris.benn...@fu-berlin.de
Re: [O] patch org-mode Makefile - solve a couple debian build problems and a slackware build problem
Bastien b...@altern.org writes: Indeed. I'll apply every patch that - doesn't break current Makefile commands - does add a new func (even tiny) for specific distro Please send some :) One way to make the whole deployment really portable could also be to pass from plain Makefile to the autoconf beast. This would also be good to detect the Emacs version and existing external libraries which maybe needed. A few other extensions already do and I think it would decrease greatly the amount of code needed (even if it would increase the hidden complexity).
[O] org-lparse-use-flashy-warning
Hi there, I don't like the flashy warnings org-odt.el produces, so I introduced this defcustom in latest git: (setq org-lparse-use-flashy-warning nil) will turn off the warnings. -- Bastien
Re: [O] org-odt and bibliography
Torsten Wagner torsten.wag...@gmail.com writes: There is jabref [1]. Exactly. I was also going to point out JabRef. I have had Bibtex illiterates manageing Bib files using JabRef. It also claims to have a Openoffice support never tried. I tried it once and it works very nice. There were annoying limitations in OOo built-in bib. manager. I know JabRef used the proper solution cause references and the litterature list was set in the document with that grey color that is also used by the TOC. Hence, if you are going to use a bib-file in OOo JabRef seems to be the way to go. Still, an Org-Centric solutoin based on \cite would be best. –Rasmus -- Sent from my Emacs
[O] Feature request or did I overlook ..
Hi all, having standard clock entries like CLOCK: [2011-07-08 Fr 08:45]--[2011-07-08 Fr 09:15] = 0:30 many a times later on I want to adjust the beginning timestamp. Moving the whole clock range backward or forward maybe half an hour is a 2 step procedure: First I have to adjust the begin timestamp, then the end timestamp. I would love something like a Ctr-Shift-Up and Ctrl-Shift-Down that moves the relating timestamp synchronously and thus leaves the time difference the same. Example1: Having point on CLOCK: [2011-07-08 Fr 08:45]--[2011-07-08 Fr 09:15] = 0:30 ^ pressing Ctr-Shift-Up 2 times I would like to end up at CLOCK: [2011-07-08 Fr 09:15]--[2011-07-08 Fr 09:45] = 0:30 ^ Example2: Having point on CLOCK: [2011-07-08 Fr 08:45]--[2011-07-08 Fr 09:15] = 0:30 ^ pressing Ctr-Shift-Down 3 times I would like to end up at CLOCK: [2011-07-08 Fr 06:15]--[2011-07-08 Fr 06:45] = 0:30 ^ I hope I could make the point clear. Maybe I overlooked the docs and such a functionality is already there. If not it could be a nice little feature. Thanks for considering, Rainer
Re: [O] working with delimited files
On Fri, Jul 08 2011,Bastien wrote: Hi Sivaram, Sivaram Neelakantan nsivaram@gmail.com writes: This makes it easier to read as you can see below | BEL | EQ | 02-Jan-2006 | 993.15 | 998 |1001 | 983 |.. | BEL | EQ | 03-Jan-2006 | 989.05 | 999.5 |1000 | 989.9 |.. | BEL | EQ | 04-Jan-2006 | 994.35 | 998 |1014 | 986.15 |.. How do I use the overlay for editing but keep the underlying file structure? I can see a solution where you could add an overlay to display the table (say, with C-u C-c |, for example) but you won't be able to *edit*. Right, I'm able to read the file as a table using C-C |, though it ends up as a changed buffer. For simple viewing, I really do not mind the current set up that just modifies the buffer I.e C-c| is good enough(an option to open read-only would be nice). However, it's the ability to use the overlay to edit and save it back in the same format as in the original file is what I was looking for. sivaram --
[O] Bug in ODT exporter
Hi! Having this simple org file DONE [#A] Test #+OPTIONS: :t - [2011-07-08 Fr] test the export with C-c C-e O stops when starting LibreOffice 3.4.1 with the message: Read Error. Format Error in textdocument content.xml at position 288,114 found. this works: DONE [#A] Test #+OPTIONS: :t - [2011-07-08 Fr] test Rainer
Re: [O] Syntax for tags-todo in org-agenda-custom-commands
Loris Bennett loris.benn...@fu-berlin.de writes: Hi Bastien, Bastien b...@altern.org writes: Hi Loris, Loris Bennett loris.benn...@fu-berlin.de writes: In my org-agenda-custom-commands I've got two block entries: tags-todo office(project|task) and tags-todo home(project|task) Items with :office:project: and :home:project: are separated properly, but :office:task: and :home:task: end up in both lists. Can you send a test file, with actual results and expected results? Test file: * Tasks:task: ** TODO Mow lawn :home: ** TODO Install R:office: * Projects :project: ** TODO Set up cluster :office: ** TODO Sort out backup:home: Actual Results: == Office agendatest: TODO Mow lawn :task::home: agendatest: TODO Install R:task::office: agendatest: TODO Set up cluster:project::office: == Home TODOs agendatest: TODO Mow lawn :task::home: agendatest: TODO Install R:task::office: agendatest: TODO Sort out backup :project::home: Expected Results: == Office agendatest: TODO Install R:task::office: agendatest: TODO Set up cluster:project::office: == Home TODOs agendatest: TODO Mow lawn :task::home: agendatest: TODO Sort out backup :project::home: I hope this is complete. I don't quite know what the best way to test something like this is without disturbing my configuration too much. I _guess_ the problem you have, but I'd like to see/test it. What should the correct syntax be and where is it described? Did you look in the manual? What is missing? I looked here http://orgmode.org/manual/Block-agenda.html#Block-agenda but there is no complex example with and-ing and or-ing tags. I see that I should also have looked here: http://orgmode.org/manual/Matching-tags-and-properties.html Thanks! Thank you for taking the time. Cheers Loris -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email loris.benn...@fu-berlin.de
Re: [O] Syntax for tags-todo in org-agenda-custom-commands
Loris Bennett loris.benn...@fu-berlin.de writes: What should the correct syntax be and where is it described? Did you look in the manual? What is missing? I looked here http://orgmode.org/manual/Block-agenda.html#Block-agenda ,[ C-h v org-agenda-custom-commands ] | matchWhat to search for: | - a single keyword for TODO keyword searches !!] - a tags match expression for tags searches [ !! | - a word search expression for text searches. | - a regular expression for occur searches | For all other commands, this should be the empty string. ` = ,[ (info (org)Matching tags and properties) ] | A search string can use Boolean operators `' for AND and `|' for OR. | `' binds more strongly than `|'. !!] Parentheses are currently not implemented. [!! | ` (Z Test home ((agenda ) (tags-todo +home+project|+home+task))) (Y Test work ((agenda ) (tags-todo +office+project|+office+task))) seems to work? Memnon
Re: [O] bug: footnotes do not export to HTML
Hello, Bernt Hansen be...@norang.ca writes: Nicolas Goaziou n.goaz...@gmail.com writes: Samuel Wales samolog...@gmail.com writes: On 2011-07-05, Nicolas Goaziou n.goaz...@gmail.com wrote: As I cannot reproduce this on my test files, I will need an ECM to debug this. Included. The bug occurs in ASCII export also. Thank you ! I have (hopefully) fixed it in master. Regards, Hi Nicolas, I'm not sure if this is related or not but now I'm getting footnotes in my HTML exports where I'm not expecting any. I think this might already have been reported but I can't find the previous post anymore. Sample org file * Using the clock history to clock in old tasks *Clock history selection buffer for C-u C-c C-x C-i* #+begin_example Default Task [d] norang Organization -- Task B The task interrupted by starting the last one [i] norang Organization -- Task B Current Clocking Task [c] org NEXT Document my use of org-mode -- Task A Recent Tasks [1] org NEXT Document my use of org-mode -- Task A [2] norang Organization -- Task B ... [Z] org DONE Fix default section links-- 35 clock task entries ago #+end_example This isn't related. Obviously, [1] org and [2] norang are recognized as footnotes. I will remove the opportunity to have footnotes in some specific contexts, like example blocks. Regards, -- Nicolas Goaziou
Re: [O] Syntax for tags-todo in org-agenda-custom-commands
Memnon Anon gegendosenflei...@googlemail.com writes: Loris Bennett loris.benn...@fu-berlin.de writes: What should the correct syntax be and where is it described? Did you look in the manual? What is missing? I looked here http://orgmode.org/manual/Block-agenda.html#Block-agenda ,[ C-h v org-agenda-custom-commands ] | matchWhat to search for: | - a single keyword for TODO keyword searches !!] - a tags match expression for tags searches [ !! | - a word search expression for text searches. | - a regular expression for occur searches | For all other commands, this should be the empty string. ` = ,[ (info (org)Matching tags and properties) ] | A search string can use Boolean operators `' for AND and `|' for OR. | `' binds more strongly than `|'. !!] Parentheses are currently not implemented. [!! | ` (Z Test home ((agenda ) (tags-todo +home+project|+home+task))) (Y Test work ((agenda ) (tags-todo +office+project|+office+task))) seems to work? Memnon Thanks, I was just being a bit dopey. I had already woken up a bit and come up with (tags-todo +office+CATEGORY=\project\|+office+CATEGORY=\task\) I think maybe I need to start a new thread some time about generally approaches to using tags vs. categories. I am sure there must a few fairly standard idioms that people are using. Cheers Loris -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email loris.benn...@fu-berlin.de
Re: [O] bug: footnotes do not export to HTML
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Bernt Hansen be...@norang.ca writes: Sample org file * Using the clock history to clock in old tasks *Clock history selection buffer for C-u C-c C-x C-i* #+begin_example Default Task [d] norang Organization -- Task B The task interrupted by starting the last one [i] norang Organization -- Task B Current Clocking Task [c] org NEXT Document my use of org-mode -- Task A Recent Tasks [1] org NEXT Document my use of org-mode -- Task A [2] norang Organization -- Task B ... [Z] org DONE Fix default section links-- 35 clock task entries ago #+end_example This isn't related. Obviously, [1] org and [2] norang are recognized as footnotes. I will remove the opportunity to have footnotes in some specific contexts, like example blocks. Thanks! -- Bernt
Re: [O] bug: footnotes do not export to HTML
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: I will remove the opportunity to have footnotes in some specific contexts, like example blocks. Wise decision -- the less feet we have, less shoots in the feet we may have. -- Bastien
Re: [O] Bug in ODT exporter
Am 08.07.2011 14:22, schrieb Rainer Stengele: Hi! Having this simple org file DONE [#A] Test #+OPTIONS: :t - [2011-07-08 Fr] test the export with C-c C-e O stops when starting LibreOffice 3.4.1 with the message: Read Error. Format Error in textdocument content.xml at position 288,114 found. this works: DONE [#A] Test #+OPTIONS: :t - [2011-07-08 Fr] test Rainer Sorry for the typo! it works, if I write DONE [#A] Test #+OPTIONS: :nil - [2011-07-08 Fr] test So if I want to export timestamps the exporter fails. Rainer
Re: [O] Bug in ODT exporter
Hi Rainer, Rainer Stengele rainer.steng...@diplan.de writes: DONE [#A] Test #+OPTIONS: :t - [2011-07-08 Fr] test Why would you put #+OPTIONS here? this works: DONE [#A] Test #+OPTIONS: :t - [2011-07-08 Fr] test What is the difference between the 2? -- Bastien
Re: [O] Calendar-like view of the org-agenda
On Wed, Jul 06, 2011 at 11:30:02AM +, Memnon Anon wrote: This is *beautiful*. I concur completely! This has filled a gap I've had for quite a while, needing to visualize org tasks across a calendar. Two minor FRs (I hope you continue to monitor the list): - 'q' key to close the calendar buffer, like org-agenda does - Support for keyword highlight, whether org keyword (TODO/DONE) and faces or otherwise. Thanks! -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] Syntax for tags-todo in org-agenda-custom-commands
Hi Loris, Loris Bennett loris.benn...@fu-berlin.de writes: I think maybe I need to start a new thread some time about generally approaches to using tags vs. categories. I am sure there must a few fairly standard idioms that people are using. Good idea. Personally, I use tags for contexts and categories for projects. -- Bastien
Re: [O] Babel: 1st version for music notation language Fomus
Torsten Anders torsten.and...@beds.ac.uk writes: Dear Eric, On 8 Jul 2011, at 02:38, Eric Schulte wrote: Thanks for sharing this, it looks great, short clear and to the point. Shall I add it to the contrib/ directory? If you think it is already at that point, that is certainly fine by me. Great, I do prefer to fold new languages in early so that they can benefit from wider use and testing. This is now located in contrib/babel/langs/. Thanks for the contribution -- Eric Best, Torsten Best -- Eric Torsten Anders torsten.and...@beds.ac.uk writes: Dear Babel developers, Inspired by the newly available Lilypond, I hacked up a first version of language support for Fomus (http://fomus.sourceforge.net/). Briefly, Fomus is a music notation system that translates a relatively simple domain specific music language into multiple output formats, including Lilypond and MusicXML (the latter is an open format supported by many commercial music notation systems such as Finale and Sibelius). In a nutshell, Fomus can simplify the generation of complex scores, because it can add various score information automatically. Anyway, please find my first attempt of a Fomus integration attached. This works already fine for standard code blocks such as the following. Note that the result of this is a Lilypond file. #+begin_src fomus :file test1.ly time 0 dur 2 pitch 60; time 2 dur 1 pitch 62; time 3 dur 1 pitch 63; time 4 dur 4 pitch 65; #+end_src Of course, because this is a quick hack, various improvements can be made. For example, it might be a good idea to allow for something like :file test.pdf, where the resulting Lilypond call would see file.ly, but the automatically inserted link in the org buffer would be the resulting file.pdf. Comments are welcome. Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://strasheela.sourceforge.net http://www.torsten-anders.de -- Eric Schulte http://cs.unm.edu/~eschulte/ -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Bug in ODT exporter
Hi Rainer, Rainer Stengele rainer.steng...@diplan.de writes: DONE [#A] Test #+OPTIONS: :nil - [2011-07-08 Fr] test So if I want to export timestamps the exporter fails. I confirm -- here is the faulty string: , | text:p text:style-name=Text_20_body | text:style-name=OrgTimestampWrapper | text:span text:style-name=OrgTimestamp2011-07-08 Fr/text:span | /text:span test ` Jambunathan, can you look at this? PS: LibreOffice gives the location (row,column) of the error. To speed debugging up, it's a good idea to include the faulty string Thanks! -- Bastien
Re: [O] Babel: 1st version for music notation language Fomus
Hi Eric, Eric Schulte schulte.e...@gmail.com writes: I do prefer to fold new languages in early so that they can benefit from wider use and testing. This is now located in contrib/babel/langs/. Thanks. I slightly updated library-of-babel.org to list existing supported languages, either in core or in contrib/babel/langs/. -- Bastien
Re: [O] Calendar-like view of the org-agenda
Russell Adams rlad...@adamsinfoserv.com writes: Two minor FRs (I hope you continue to monitor the list): https://github.com/kiwanami/emacs-calfw/issues ? - 'q' key to close the calendar buffer, like org-agenda does ,[ https://github.com/kiwanami/emacs-calfw/pull/4 ] TSDH: aee24d8 Bind q to bury-buffer in calendar buffer | [...] KIWA: I'm going to check them and would merge them. ` Memnon
[O] [PATCH] ob-lilypond.el compiler error fix org-babel-tangle not defined function
--- diff --git a/lisp/ob-lilypond.el b/lisp/ob-lilypond.el index 6971a69..5a08ca4 100644 --- a/lisp/ob-lilypond.el +++ b/lisp/ob-lilypond.el @@ -30,6 +30,7 @@ ;;; Code: (require 'ob) (require 'ob-eval) +(require 'ob-tangle) ;;compiler requesting fun org-babel-tangle (defalias 'lilypond-mode 'LilyPond-mode) (declare-function show-all outline ()) --- ob-lilypond.el.diff Description: Binary data
[O] 7.6 and Thanks
Thanks for all the work everyone puts in on this list and on this project. Org-Mode has really gotten me squared away and keeps things organized for me. In an effort to try and start help giving back I just submitted a patch reference a compiler error. I know they aren't high priority necessarily but I do know they have to get cleaned up from time to time. I applied it on my local branch and it appears to have fixed the problem : -cut here--cut here-- In end of data: ob-lilypond.el:447:1:Warning: the function `org-babel-tangle' is not known to be defined. --cut herecut here-- any feedback reference the patch I just submitted (better ways to have accomplished eliminating this error, etc are greatly appreciated as I am new to using git and working in a community and I am trying to learn. Again, thanks to everyone for the help. Matthew
Re: [O] Babel: 1st version for music notation language Fomus
Bastien b...@altern.org writes: Hi Eric, Eric Schulte schulte.e...@gmail.com writes: I do prefer to fold new languages in early so that they can benefit from wider use and testing. This is now located in contrib/babel/langs/. Thanks. I slightly updated library-of-babel.org to list existing supported languages, either in core or in contrib/babel/langs/. Thanks for making this change. -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] [babel] inline call within table formula?
Hi, Quick question: I'd like to use a babel inline call to calculate something in a table based on other values in the table. Is this possible? Probably using elisp directly? If so, I cannot figure out what the magic incantation should be! I hope somebody can help. For illustration, I'd like to do something like this: --8---cut here---start-8--- #+source: f #+begin_src octave :var x=[1 3 5] sin(x) #+end_src | x1 | x2 | x3 | f| |+++--| | 1 | 3 | 5 | Apply call_f($1..$3) here | --8---cut here---end---8--- Thanks, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.6 (release_7.6.4.gf305a)
Re: [O] [PATCH] ob-lilypond.el compiler error fix org-babel-tangle not defined function
Hi Matthew, Matthew Sauer improv.philoso...@gmail.com writes: --- diff --git a/lisp/ob-lilypond.el b/lisp/ob-lilypond.el index 6971a69..5a08ca4 100644 --- a/lisp/ob-lilypond.el +++ b/lisp/ob-lilypond.el @@ -30,6 +30,7 @@ ;;; Code: (require 'ob) (require 'ob-eval) +(require 'ob-tangle) ;;compiler requesting fun org-babel-tangle (defalias 'lilypond-mode 'LilyPond-mode) (declare-function show-all outline ()) Applied, thanks! -- Bastien
Re: [O] [PATCH] ob-lilypond.el compiler error fix org-babel-tangle not defined function
I don't see this error when running make, I'm using the Emacs git head, perhaps this is Emacs version specific? -- Eric Matthew Sauer improv.philoso...@gmail.com writes: --- diff --git a/lisp/ob-lilypond.el b/lisp/ob-lilypond.el index 6971a69..5a08ca4 100644 --- a/lisp/ob-lilypond.el +++ b/lisp/ob-lilypond.el @@ -30,6 +30,7 @@ ;;; Code: (require 'ob) (require 'ob-eval) +(require 'ob-tangle) ;;compiler requesting fun org-babel-tangle (defalias 'lilypond-mode 'LilyPond-mode) (declare-function show-all outline ()) --- -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] 7.6 and Thanks
Hi Matthew, Matthew Sauer improv.philoso...@gmail.com writes: Thanks for all the work everyone puts in on this list and on this project. Org-Mode has really gotten me squared away and keeps things organized for me. In an effort to try and start help giving back I just submitted a patch reference a compiler error. I know they aren't high priority necessarily but I do know they have to get cleaned up from time to time. Every contribution is welcome - thanks! -- Bastien
Re: [O] LaTex export: How to use `csquotes' and `\enquote{}'
Am 08.07.2011 04:09, schrieb Nick Dokos:
Thomas S. Dyet...@tsdye.com wrote:
Hi Nick,
Good point.
How about three new variables, org-export-latex-open-double-quotes,
org-export-latex-close-double-quotes, and org-export-latex-single-quote?
The regexp stuff could stay as hard code and the user would only be able
to mess up what actually ends up being exported.
That's a pretty good idea: simple implementation, no extra options,
set-and-forget
and it only affects the latex exporter.
Tom, you win the jackpot: you'll have the patch ready by tomorrow?
Nick
I agree with Nick - simple and clean.
What would be the purpose of the variable
`org-export-latex-single-quote'? If you intend to support \enquote*{,
then perhaps there should be an additional variable for the single
closing quote (which would be `}' again...)
Then you'd have four variables:
org-export-latex-open-double-quotes
org-export-latex-close-double-quotes
org-export-latex-open-single-quote
org-export-latex-close-single-quote
But perhaps I'm misguided...
Regards.
All the best,
Tom
=20
Nick Dokosnicholas.do...@hp.com writes:
Responses to Frederik and Tom inline.
Frederikfreak.f...@gmail.com writes:
Why not use one option for babel and another for csquotes? I thought
of something like this:
#+OPTIONS: babel:english,ngerman csquotes:autostyle,german=3Dguillemets
I did suggest different options, one controlling babel and the other
controlling csquotes. The problem with the above is that it is very
LaTeX-specific: the options and their values have no meaning outside of
that. I think that we should strive to use more generic options that
would at least be usable by other export engines.
Or is there any other reason why one would like to specify language opti=
ons?
Sadly I don't have the skills to suggest a patch...
I definitely see Nick's point: simplicity is one of the most important
features of org-mode. So a possible decision not to support csquotes
is absolutely understandable.
I'll be very surprised if there is no support for csquotes within a couple
of weeks (maybe within a couple of days :-) ) The question is what form
will it take?
Thomas S. Dyet...@tsdye.com wrote:
I'm wondering if a simpler solution than Nick's might be to replace the
lists at the end of this code snippet with a variable, say
org-export-latex-quote-mechanism. Initially, the variable would be set
to the second list. If the user wanted something different, then the
user would be responsible for setting the variable to the different
quoting mechanism, whether it be \enquote{ or something else. The user
would also be responsible for making sure the LaTeX packages needed to
support the quoting mechanism were loaded and functional.
=20
(defun org-export-latex-quotation-marks ()
Export quotation marks depending on language conventions.
(let* ((lang (plist-get org-export-latex-options-plist :language))
(quote-rpl (if (equal lang fr)
'((\\(\\s-\\)\ =C2=AB~)
(\\(\\S-\\)\ ~=C2=BB)
(\\(\\s-\\)' `))
'((\\(\\s-\\|[[(]\\)\ ``)
(\\(\\S-\\)\ '')
(\\(\\s-\\|(\\)' `)
=20
This might provide Org-mode the flexibility needed to support csquotes,
but also leave open the possibility of supporting other packages, as
well.
=20
Maybe - this is the kind of mechanism that is used for
org-export-latex-classes for example, so there is definitely
precedent. OTOH, the lists above look like hen scratchings (or line
noise if you prefer, or -- I'll get in trouble for this -- Perl
code :-)), so it would be easy to get things wrong if you have to
cut-and-paste-and-edit which I think one would have to do to customize
it: it's OK to expect *one* developer to get it right, but it's not
OK to expect 100 users to get it right.
So it might be simpler to implement, but I'm not sure it might be
simpler to use. I've supported using existing mechanisms to implement
new behavior before and not disturbing the existing structure too much
(e.g. the revtex stuff that Sebastian Hoffert was (is?) working on).
But if it leads to e.g. an implementation that befuddles users, then
you end up with a flood of questions on the ML. So it's a balancing
act.
BTW, you mention the possibility of supporting other packages. I didn't
find anything useful in the TeX FAQ but if there are csquotes-like
packages that people commonly (or perhaps uncommonly) use then a survey
of their capabilities might indicate the best way to go.
Nick
--=20
Thomas S. Dye
http://www.tsdye.com
--
Frederik
Re: [O] 7.6 and Thanks
Bastien, Thanks! I was just hoping to make sure that I had made the correction in an appropriate fashion for those on this project (having it require the file that had the function defined instead of re-defining the file). I am still relatively new here, new to elisp and git. Again, thanks for all you do. On Fri, Jul 8, 2011 at 10:35 AM, Bastien b...@altern.org wrote: Hi Matthew, Matthew Sauer improv.philoso...@gmail.com writes: Thanks for all the work everyone puts in on this list and on this project. Org-Mode has really gotten me squared away and keeps things organized for me. In an effort to try and start help giving back I just submitted a patch reference a compiler error. I know they aren't high priority necessarily but I do know they have to get cleaned up from time to time. Every contribution is welcome - thanks! -- Bastien
Re: [O] [PATCH] ob-lilypond.el compiler error fix org-babel-tangle not defined function
Eric Schulte schulte.e...@gmail.com writes: I don't see this error when running make, I'm using the Emacs git head, perhaps this is Emacs version specific? I don't think so: in ob-lilypond.el, the `ly-tangle' function calls `org-babel-tangle', so requiring ob-tangle.el seems the right thing to do here. No? -- Bastien
Re: [O] Thanks for Lilypond export (and minor comments)
Hi Bastien, On Fri, 08 Jul 2011 11:08:07 +0200 Bastien b...@altern.org wrote: As long that I'm confident many testers use the latest master branch, I'm reluctant to go through the hassle of cherry-picking commits... and just release a minor release with all latest dev from master. Call me lazy, but I'd rather keeping things simple here. Maybe the development model followed by git itself would be a good solution (merges instead of cherry-picking)? Although I fear org is a much smaller project compared to git and it could be an overkill. http://www.kernel.org/pub/software/scm/git/docs/howto/maintain-git.txt Hope this helps. -- Suvayu Open source is the future. It sets us free.
Re: [O] Release 7.6
After every release there are messages like this. And Memmon is right. It cannot be said too often. Thank you everyone for your hard work. On 7/07/11 11:01 AM, Achim Gratz strom...@nexgo.de wrote: Bastien b...@altern.org writes: I'm releasing Org 7.6. Thank you and everyone else for all the work that has been put into this release. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada The information contained in this message is confidential. It is intended to be read only by the individual or entity named above or their designee. If the reader of this message is not the intended recipient, you are hereby notified that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message.
Re: [O] LaTex export: How to use `csquotes' and `\enquote{}'
Frederik freak.f...@gmail.com writes:
Am 08.07.2011 04:09, schrieb Nick Dokos:
Thomas S. Dyet...@tsdye.com wrote:
Hi Nick,
Good point.
How about three new variables, org-export-latex-open-double-quotes,
org-export-latex-close-double-quotes, and org-export-latex-single-quote?
The regexp stuff could stay as hard code and the user would only be able
to mess up what actually ends up being exported.
That's a pretty good idea: simple implementation, no extra options,
set-and-forget
and it only affects the latex exporter.
Tom, you win the jackpot: you'll have the patch ready by tomorrow?
Nick
I agree with Nick - simple and clean.
What would be the purpose of the variable
org-export-latex-single-quote'? If you intend to support \enquote*{,
then perhaps there should be an additional variable for the single
closing quote (which would be `}' again...)
Then you'd have four variables:
org-export-latex-open-double-quotes
org-export-latex-close-double-quotes
org-export-latex-open-single-quote
org-export-latex-close-single-quote
But perhaps I'm misguided...
Regards.
Hi Frederik,
I think you're right. I was looking at the existing code, which has
three list entries, and not thinking through to the csquotes solution.
Thanks for pointing this out.
All the best,
Tom
All the best,
Tom
=20
Nick Dokosnicholas.do...@hp.com writes:
Responses to Frederik and Tom inline.
Frederikfreak.f...@gmail.com writes:
Why not use one option for babel and another for csquotes? I thought
of something like this:
#+OPTIONS: babel:english,ngerman csquotes:autostyle,german=3Dguillemets
I did suggest different options, one controlling babel and the other
controlling csquotes. The problem with the above is that it is very
LaTeX-specific: the options and their values have no meaning outside of
that. I think that we should strive to use more generic options that
would at least be usable by other export engines.
Or is there any other reason why one would like to specify language opti=
ons?
Sadly I don't have the skills to suggest a patch...
I definitely see Nick's point: simplicity is one of the most important
features of org-mode. So a possible decision not to support csquotes
is absolutely understandable.
I'll be very surprised if there is no support for csquotes within a couple
of weeks (maybe within a couple of days :-) ) The question is what form
will it take?
Thomas S. Dyet...@tsdye.com wrote:
I'm wondering if a simpler solution than Nick's might be to replace the
lists at the end of this code snippet with a variable, say
org-export-latex-quote-mechanism. Initially, the variable would be set
to the second list. If the user wanted something different, then the
user would be responsible for setting the variable to the different
quoting mechanism, whether it be \enquote{ or something else. The user
would also be responsible for making sure the LaTeX packages needed to
support the quoting mechanism were loaded and functional.
=20
(defun org-export-latex-quotation-marks ()
Export quotation marks depending on language conventions.
(let* ((lang (plist-get org-export-latex-options-plist :language))
(quote-rpl (if (equal lang fr)
'((\\(\\s-\\)\ =C2=AB~)
(\\(\\S-\\)\ ~=C2=BB)
(\\(\\s-\\)' `))
'((\\(\\s-\\|[[(]\\)\ ``)
(\\(\\S-\\)\ '')
(\\(\\s-\\|(\\)' `)
=20
This might provide Org-mode the flexibility needed to support csquotes,
but also leave open the possibility of supporting other packages, as
well.
=20
Maybe - this is the kind of mechanism that is used for
org-export-latex-classes for example, so there is definitely
precedent. OTOH, the lists above look like hen scratchings (or line
noise if you prefer, or -- I'll get in trouble for this -- Perl
code :-)), so it would be easy to get things wrong if you have to
cut-and-paste-and-edit which I think one would have to do to customize
it: it's OK to expect *one* developer to get it right, but it's not
OK to expect 100 users to get it right.
So it might be simpler to implement, but I'm not sure it might be
simpler to use. I've supported using existing mechanisms to implement
new behavior before and not disturbing the existing structure too much
(e.g. the revtex stuff that Sebastian Hoffert was (is?) working on).
But if it leads to e.g. an implementation that befuddles users, then
you end up with a flood of questions on the ML. So it's a balancing
act.
BTW, you mention the possibility of supporting other packages. I didn't
find anything useful in the TeX FAQ but if there are csquotes-like
packages that people commonly (or perhaps uncommonly) use then a survey
of their capabilities might indicate the best way to go.
Nick
--=20
Thomas S. Dye
http://www.tsdye.com
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] bug: footnotes do not export to HTML
Hello, Bastien b...@altern.org writes: Nicolas Goaziou n.goaz...@gmail.com writes: I will remove the opportunity to have footnotes in some specific contexts, like example blocks. Wise decision -- the less feet we have, less shoots in the feet we may have. Done. Footnotes cannot live anymore in example, src, verse, latex, html and docbook blocks. Wherever we were, we're now six feet under, I guess. Regards, -- Nicolas Goaziou
Re: [O] bug: footnotes do not export to HTML
Nicolas Footnotes cannot live anymore in example, src, verse, latex, html and docbook blocks. In org-footnote-forbidden-blocks '(example verse src latex html docbook) should we make use of org-export-backends. I introduced the above variable as part of org-odt compatibility changes. ,[ C-h v org-export-backends RET ] | org-export-backends is a variable defined in `org-exp.el'. | Its value is (odt docbook html beamer ascii latex) | | | Documentation: | List of Org supported export backends. | | [back] ` Wherever we were, we're now six feet under, I guess. Regards, --
[O] Problem with latex and footnotes
Hi. I'm noticed a problem with latex equations and footnotes. I'm not
sure, but I believe it started after I downloaded the newest version
of org-mode.
When I try to export a $...$ block that is inside a footnote, the
latex file end up with \$...\$ instead of $...$. As an example, this:
#+LaTeX_CLASS: article
* test
This is just a test [fn:test].
[fn:test] This is an equation: $x = y$.
Gets exported into this (just the relevant section):
\section{test}
\label{sec-1}
This is just a test \footnote{This is an equation: \$x = y\$. }.
Is there a way around it?
Thanks in advance.
---
Rafael Calsaverini
Dep. de Física Geral, Sala 336
Instituto de Física - Universidade de São Paulo
rafael.calsaver...@gmail.com
http://stoa.usp.br/calsaverini/weblog
CEL: (11) 7525-6222
USP: (11) 3091-6803
Re: [O] Problem with latex and footnotes
Rafael Calsaverini rafael.calsaver...@gmail.com wrote: Hi. I'm noticed a problem with latex equations and footnotes. I'm not sure, but I believe it started after I downloaded the newest version of org-mode. When I try to export a $...$ block that is inside a footnote, the latex file end up with \$...\$ instead of $...$. As an example, this: #+LaTeX_CLASS: article * test This is just a test [fn:test]. [fn:test] This is an equation: $x = y$. This works: --8---cut here---start-8--- #+LaTeX_CLASS: article * test This is just a test [fn:test]. [fn:test] This is an equation: \(x = y\). --8---cut here---end---8--- It is generally a good idea (and not just in org-mode) to avoid $...$ and $$...$$ for math. The recommended way is \(...\) for inline equations and \[...\] for diplayed math. Nick
[O] Don't ask, don't run
Hi, I know from the manual that I can set 'org-confirm-babel-evaluate' to t, or nil, or a function, to control whether I'm asked permission to run a code block. However, that only gives me two choices - ask the user, or pretend the user said yes. Sometimes I'd like to pretend the user said no, without asking. Specifically, I'd like to always manually control when code blocks are executed. When exporting, I don't want them executed (and I don't want to be asked about my dozens of blocks each time). When hitting C-c C-c manually, I just want it to run (and I don't want to be asked whether I'm sure). Is there a similar variable, or perhaps an export option, that will give me this kind of workflow? Thanks. -- Ken Williams Senior Research Scientist Thomson Reuters http://labs.thomsonreuters.com
Re: [O] bug: footnotes do not export to HTML
Jambunathan K kjambunat...@gmail.com writes: In org-footnote-forbidden-blocks '(example verse src latex html docbook) should we make use of org-export-backends. I introduced the above variable as part of org-odt compatibility changes. ,[ C-h v org-export-backends RET ] | org-export-backends is a variable defined in `org-exp.el'. | Its value is (odt docbook html beamer ascii latex) | | | Documentation: | List of Org supported export backends. | | [back] ` Indeed, I am going to make use of it. I will also change `org-footnote-forbidden-blocks' and `org-list-forbidden-blocks' into defconsts as they are not meant to be modified anyway. Thanks for notifying me about this variable. Regards, -- Nicolas Goaziou
Re: [O] Don't ask, don't run
ken.willi...@thomsonreuters.com writes: Hi, I know from the manual that I can set 'org-confirm-babel-evaluate' to t, or nil, or a function, to control whether I'm asked permission to run a code block. However, that only gives me two choices - ask the user, or pretend the user said yes. Sometimes I'd like to pretend the user said no, without asking. Specifically, I'd like to always manually control when code blocks are executed. When exporting, I don't want them executed (and I don't want to be asked about my dozens of blocks each time). When hitting C-c C-c manually, I just want it to run (and I don't want to be asked whether I'm sure). Is there a similar variable, or perhaps an export option, that will give me this kind of workflow? Thanks. I can't help you directly although I also often want the behaviour you are describing. One workaround that should give you what you want is to enable evaluation without prompting (org-confirm-babel-evaluate: nil) and to have the results from runs cached so that, when exporting, the source code blocks shouldn't have to execute; see [[info:org#cache]]. -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.6 (release_7.6.4.gf305a)
Re: [O] Thanks for Lilypond export (and minor comments)
Bastien b...@altern.org writes: is there a process for bug-fix commits like this one which should be pushed through to Emacs24? I'm thinking a branch (maintenance?) to which this should be pushed or a special way to tag the commit? there is none for now -- I need to think about it. Pure fixes should probably be applied on top of maint and then merged into master (not cherry-picked from master to maint, this would create duplicate history). On occasion this might produce a merge conflict, but these instances should be rare. That way maint would be a stable, but still regularly bugfixed branch without having all the excitement of living on master and having old features pulled from under you while the new features aren't quite there yet. If any larger bugs crop up, you can always tag a sub-release on maint and create a package for anyone not using git. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] Bug in ODT exporter
Rainer Thanks for reporting the bug. I have pushed a fix few moments ago. Could you please try again? The problem was that timestamps were occuring as list item in the example you provided which confused the exporter. If you encounter corruption issue or issues related to formatting of odt file you can identify the root cause as below: 1. Switch to *.odt buffer (C-x b whatever.odt) 2. Open the content.xml (Hit RET on content.xml) 3. Do a C-u C-c C-n (M-x rng-first-error) 4. Note the error message as well as the XML stuff at the point of error. Once the error is identified, you can create a minimal org file for reproducing the bug very easily. Jambunathan K. Am 08.07.2011 14:22, schrieb Rainer Stengele: Hi! Having this simple org file DONE [#A] Test #+OPTIONS: :t - [2011-07-08 Fr] test the export with C-c C-e O stops when starting LibreOffice 3.4.1 with the message: Read Error. Format Error in textdocument content.xml at position 288,114 found. this works: DONE [#A] Test #+OPTIONS: :t - [2011-07-08 Fr] test Rainer Sorry for the typo! it works, if I write DONE [#A] Test #+OPTIONS: :nil - [2011-07-08 Fr] test So if I want to export timestamps the exporter fails. Rainer --
Re: [O] patch org-mode Makefile - solve a couple debian build problems and a slackware build problem
Nick Dokos nicholas.do...@hp.com writes: Most Linux systems I know of have a description of what distro is installed in the /etc/issue file: Ubuntu, Debian, RH, Fedora, SuSE [...] True, but it's not reliable since it is quite common to customize the login message. And the next thing of course is that you don't have that file at all on Windows, where the Makefile should also work. I the dark ages when different makes ruled, it was common to have Makefile.vms Makefile.SysV or something like that. Maybe something along those lines plus some notes in README or an additonal INSTALL would be more appropriate? Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [O] Calendar-like view of the org-agenda
Russell Adams rlad...@adamsinfoserv.com writes: Hi Russell, This is *beautiful*. I concur completely! This has filled a gap I've had for quite a while, needing to visualize org tasks across a calendar. Two minor FRs (I hope you continue to monitor the list): - 'q' key to close the calendar buffer, like org-agenda does In my github fork, I've already bound `q' to `bury-buffer' which does what you want. Masashi is reviewing my changes and hopefully pull. I've also made the characters used for table rendering customizable, so that you can use nice unicode glyphs. http://dl.dropbox.com/u/30611246/img/calfw-unicode.png Bye, Tassilo
Re: [O] patch org-mode Makefile - solve a couple debian build problems and a slackware build problem
Achim Gratz strom...@nexgo.de wrote: Nick Dokos nicholas.do...@hp.com writes: Most Linux systems I know of have a description of what distro is installed in the /etc/issue file: Ubuntu, Debian, RH, Fedora, SuSE [...] True, but it's not reliable since it is quite common to customize the login message. And the next thing of course is that you don't have that file at all on Windows, where the Makefile should also work. I the dark ages when different makes ruled, it was common to have Makefile.vms Makefile.SysV or something like that. Maybe something along those lines plus some notes in README or an additonal INSTALL would be more appropriate? I'm actually hoping that nothing of the sort will be needed, but given that I don't have either debian squeeze or slackware available, I can't really see what goes wrong. As for /etc/issue, you are probably right: I never touch it but that means nothing. OTOH, it does illustrate how to make Makefiles do stupid pet tricks. Nick
[O] Question to the list about csquotes
There's been a recent discussion about using csquotes in the latex exporter[fn:1] and Tom Dye came up with a good idea of how to implement it. We have been discussing it off list but there is a point that might benefit from more general airing, so I offered to solicit opinions on the list. The question is about the following bit of code in org-export-latex-quotation-marks: , | ... | (let* ((lang (plist-get org-export-latex-options-plist :language)) |(quote-rpl (if (equal lang fr) | '((\\(\\s-\\)\ «~) | (\\(\\S-\\)\ ~») | (\\(\\s-\\)' `)) | '((\\(\\s-\\|[[(]\\)\ ``) | (\\(\\S-\\)\ '') | (\\(\\s-\\|(\\)' `) | ... ` The question is what to do about the lang = fr case (which I think we all agree is a hack): o leave it alone and implement the csquotes mechanism on top of it? o get rid of it and depend on the general csquotes mechanism to replace it? The first solution perpetuates the hack but leaves existing org files that use it unaffected. The second cleans up the hack but at the cost of some backward inompatibility: files that use the hack will not get guillemets unless some (one-time) customizations are done: the LaTeX preamble has to be expanded to pull in the appropriate packages (babel and csquotes) and a couple of string variables have to be set to the right values. So we turn to the collective wisdom of the list: how important is backward compatibility in this case (i.e. are there lots of files out there that use the hack)? And if it is important, how would you weigh the inconvenience of the required customizations against the code cleanup? Presumably, french speakers have been the heaviest users of this, so we'd like to hear from you - but opinions are welcome. Thanks, Nick Footnotes: [fn:1] http://thread.gmane.org/gmane.emacs.orgmode/43689
Re: [O] Problem with latex and footnotes
Hummm... thanks for the tip! It works now. :D --- Rafael Calsaverini Dep. de Física Geral, Sala 336 Instituto de Física - Universidade de São Paulo rafael.calsaver...@gmail.com http://stoa.usp.br/calsaverini/weblog CEL: (11) 7525-6222 USP: (11) 3091-6803 On Fri, Jul 8, 2011 at 15:26, Nick Dokos nicholas.do...@hp.com wrote: Rafael Calsaverini rafael.calsaver...@gmail.com wrote: Hi. I'm noticed a problem with latex equations and footnotes. I'm not sure, but I believe it started after I downloaded the newest version of org-mode. When I try to export a $...$ block that is inside a footnote, the latex file end up with \$...\$ instead of $...$. As an example, this: #+LaTeX_CLASS: article * test This is just a test [fn:test]. [fn:test] This is an equation: $x = y$. This works: --8---cut here---start-8--- #+LaTeX_CLASS: article * test This is just a test [fn:test]. [fn:test] This is an equation: \(x = y\). --8---cut here---end---8--- It is generally a good idea (and not just in org-mode) to avoid $...$ and $$...$$ for math. The recommended way is \(...\) for inline equations and \[...\] for diplayed math. Nick
Re: [O] org-odt (Applying custom templates)
Vinh Suppose I have styles.xml and ./Pictures/1274034B83A526F3.png in the working directory of my org file, both extracted from my original odt file that I did myself. What exactly must I do to get these files packaged into the generated odt file? How do I set org-export-odt-styles-file in my org file? I have answered your question here. http://lists.gnu.org/archive/html/emacs-orgmode/2011-03/msg01512.html. If you tell me what aspects are confusing I am willing to clarify. I would appreciate if you could test it out on the org-odt that comes with the contrib/lisp dir of git archive. Thanks! -- Vinh --
