Hello,
Just to tell you that I will make a presentation on Org-mode during the LaTeX
day in Dunkerque (FR) on Wed 13th June 2012.
Here is my summary in English for the 1:30 presentation:
You wish to write high-quality documents or presentations, whose
successive versions are easy to comp
Hi,
On Tue, Apr 24, 2012 at 1:08 AM, Bastien wrote:
> Henning Weiss writes:
>
> > it turns out that there are a couple of problems with that particular
> > patch. Some issues have already been fixed with the help of someone
> > else from the mobileorg community, but more work is required. As so
Bastien & team,
I must applaud you once again. I just refreshed my setup, jumping from
7.01 to 7.8.10 and Org didn't skip a beat.
Fantastic work!
On Thu, May 17, 2012 at 12:04:31AM +0200, Bastien wrote:
> Hi folks,
>
> I released Org 7.8.10, a bugfix-only release.
>
> http://orgmode.org/org-7.
For a long time, I've been updating org from git every week or two via:
update-org () {
(cd $HOME/SOFTWARE/EMACS/org-mode && git pull && make)
}
and I have emacs pointed at that directory. This is on NetBSD where
"make" is BSD make.
Today, I updated again and got:
make: "/home/gd
Pulling just now I get:
,
| $ git checkout master
| Switched to branch 'master'
| Your branch is behind 'origin/master' by 15 commits, and can be
fast-forwarded.
|
| $ tsocks make update
| git remote update
| Fetching origin
| Fetching github
| Fetching org-odt
| git pull
| Updating 946230b.
Hi,
I am working with Xubuntu 12.04 on a MacBook Air (4,1) with org-mode version
7.8.09. I use the following code to get "Wrap at Window Edge" in
org-agenda-mode:
,
| (add-hook 'org-agenda-mode-hook
| '(lambda()
|(if truncate-lines (toggle-truncate-lines -1))
|
On Tue, May 22, 2012 at 05:49:00PM +0200, Marius Hofert wrote:
> Hi,
>
> I am working with Xubuntu 12.04 on a MacBook Air (4,1) with org-mode version
> 7.8.09. I use the following code to get "Wrap at Window Edge" in
> org-agenda-mode:
>
> ,
> | (add-hook 'org-agenda-mode-hook
> | '(lambd
Hi Tom,
On Mon, May 21, 2012 at 3:29 PM, Tom Regner wrote:
> Hi,
>
> suvayu ali writes:
>
>> I see source blocks formated as example blocks. Is that the same as you
>> are seeing? If so, I wouldn't call that support for source blocks. I
>> would expect to see syntax highlighting like pure source
On Tue, May 22, 2012 at 9:24 PM, suvayu ali wrote:
> Hi Tom,
>
> On Mon, May 21, 2012 at 3:29 PM, Tom Regner wrote:
>> Hi,
>>
>> suvayu ali writes:
>>
>>> I see source blocks formated as example blocks. Is that the same as you
>>> are seeing? If so, I wouldn't call that support for source blocks
Dear Russell,
I thought so, too, but it does not properly wrap standard .org files (including
sections etc.). Instead of Wrap at Window Edge, I still obtain "Truncate Long
Lines"
mode in .org files.
Cheers,
Marius
Hi Greg,
Greg Troxel writes:
> For a long time, I've been updating org from git every week or two via:
>
> update-org () {
> (cd $HOME/SOFTWARE/EMACS/org-mode && git pull && make)
> }
>
> and I have emacs pointed at that directory. This is on NetBSD where
> "make" is BSD make.
>
> To
Hi Nick,
Nick Dokos writes:
> | Loading /home/nick/src/emacs/org/org-mode/lisp/org-compat.el (source)...
> | Loading /home/nick/src/emacs/org/org-mode/UTILITIES/org-fixup.el (source)...
> | Wrong number of arguments: (lambda nil (with-temp-buffer
> | (set-visited-file-name "org-install.el") (ins
Russell Adams writes:
> Bastien & team,
>
> I must applaud you once again. I just refreshed my setup, jumping from
> 7.01 to 7.8.10 and Org didn't skip a beat.
>
> Fantastic work!
Thanks!
A team work really -- and glad to see old-timers still using Org :)
--
Bastien
The code segment you posed earlier with the lambda statement may
override that behavior. Have you tried removing that and restarting
emacs?
On Tue, May 22, 2012 at 06:14:07PM +0200, Marius Hofert wrote:
> Dear Russell,
>
> I thought so, too, but it does not properly wrap standard .org files
> (in
Hi,
while trying to include a source file in a list element via #+INCLUDE, I
discovered the following behavior: A comment between two list elements breaks
the list into two lists when exporting. For example:
* Test
- This is a list element.
# This isn't.
- This is another list element.
Becom
Dear Russell,
thanks for helping.
Yes. I even removed ~/.emacs.desktop and restarted. Still, a standard
.org file is shown in "Truncate Long Lines" mode instead of (the overall
emacs default) "Wrap at Window Edge".
Cheers,
Marius
--
ETH Zurich
Dr. Marius Hofert
RiskLab, Department of Math
Hi Marius,
Marius Hofert writes:
> I am working with Xubuntu 12.04 on a MacBook Air (4,1) with org-mode version
> 7.8.09. I use the following code to get "Wrap at Window Edge" in
> org-agenda-mode:
>
> ,
> | (add-hook 'org-agenda-mode-hook
> | '(lambda()
> | (if truncate-lines
Hi Bastien,
Many thanks, that's exactly what I was looking for!
Cheers,
Marius
05/22/2012 07:21 PM, Bastien wrote:
Hi Marius,
Marius Hofert writes:
I am working with Xubuntu 12.04 on a MacBook Air (4,1) with org-mode version
7.8.09. I use the following code to get "Wrap at Window Edge" in
Hi Henning,
Henning Weiss writes:
> I have refined the edit nodes patch. Aaron Peromsik has helped me
> with developing and testing it. He hasn't reported any problems with
> it and I have been using it for a couple of weeks now without
> experiencing any problems.
Thanks. Can someone else tes
Hi François,
François Pinard writes:
> Page http://orgmode.org/worg/org-contrib/org-drill.html refers to
> inexisting http://orgmode.org/worg/org-contrib/spanish.html. There is
> no spanish.org in the Org mode distribution either. Maybe here?
>
>https://bitbucket.org/eeeickythump/org-drill
Bastien wrote:
> Hi Nick,
>
> Nick Dokos writes:
>
> > | Loading /home/nick/src/emacs/org/org-mode/lisp/org-compat.el (source)...
> > | Loading /home/nick/src/emacs/org/org-mode/UTILITIES/org-fixup.el
> > (source)...
> > | Wrong number of arguments: (lambda nil (with-temp-buffer
> > | (set-vi
Can there be an #+OPTION to stop comments and weblinks from being coloured and
names of directories from being italised, /etc/
Best wishes,
Enda
Enda wrote:
> Can there be an #+OPTION to stop comments and weblinks from being
> coloured and names of directories from being italised, /etc/
>
In what context?
Nick
Nick Dokos writes:
> Enda wrote:
>
>> Can there be an #+OPTION to stop comments and weblinks from being
>> coloured and names of directories from being italised, /etc/
>
> In what context?
I guess the OP wants to hit M-x customize-face RET on comments and
links.
2 cents,
--
Bastien
Bastien wrote:
> Nick Dokos writes:
>
> > Enda wrote:
> >
> >> Can there be an #+OPTION to stop comments and weblinks from being
> >> coloured and names of directories from being italised, /etc/
> >
> > In what context?
>
> I guess the OP wants to hit M-x customize-face RET on comments and
>
Nick Dokos writes:
> BTW, we now have four cents between us.
Yes -- one day I'll count how much money has been spent in emails
that never got answered back :)
--
Bastien
I think comments don't get exported, so it must be just regular Org?
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Samuel Wales writes:
> I think comments don't get exported, so it must be just regular Org?
Indeed. Hence my guess.
Thanks Samuel! We spend cents, you spread wisdom :)
--
Bastien
Hi François,
François Pinard writes:
> A good way to study the
> new exporter's opinion would be for me to write a Python parser which
> yields exactly the same analysis. That parser could usefully replace
> many Python scripts here which decipher Org files according to my mental
> fuzzy approx
Nick Dokos writes:
> OTOH, some maintainers would prefer emailed patches instead;
FWIW, I prefer patches sent to this list for two reasons: they get
quickly tested by many people (i.e. faster than external branches)
and bacause patches get caught on the patchwork. Even if i don't
use the patch
François Pinard writes:
>Emphasis and monospace
>--
>
>You can make words *bold*, /italic/, _underlined_, `=code=' and
>`~verbatim~', and, if you must, `+strike-through+'. Text in the code
>and verbatim string is not processed for Org mode specific syn
suvayu ali writes:
>> Only sufficient demand for org-documents will foster betterment I guess.
>
> Yes I realise that. I have never interacted with GitHub staff for
> feature requests. Being a long time org-mode user (post-6.33, that's
> ages in org years :-p), maybe I should give that a try.
I
Puneeth Chaganti writes:
> I've tweeted to them at least a couple of times (in the past few
> months) regarding this, but haven't yet got any response from them.
> May be someone should send an email to supp...@github.com. I got back
> replies for other things in about a week or so, on email. I
Hi François,
François Pinard writes:
> This (partly) replies to the message I sent a few minutes ago. Before
> sending that message, I checked in the Org manual, and the manual is
> silent about the possibility of such escaping.
>
> The manual is also silent about nesting, which has been mentio
Hi Fabrice,
"Fabrice Niessen"
writes:
> Just to tell you that I will make a presentation on Org-mode during the LaTeX
> day in Dunkerque (FR) on Wed 13th June 2012.
Great -- let's us know if the audience asks questions that are worth
asking here!
Good luck,
--
Bastien
On Tue, May 22, 2012 at 7:54 PM, Bastien wrote:
> Hi Henning,
>
> Henning Weiss writes:
>
> > I have refined the edit nodes patch. Aaron Peromsik has helped me
> > with developing and testing it. He hasn't reported any problems with
> > it and I have been using it for a couple of weeks now witho
Bastien wrote:
> Samuel Wales writes:
>
> > I think comments don't get exported, so it must be just regular Org?
>
> Indeed. Hence my guess.
>
> Thanks Samuel! We spend cents, you spread wisdom :)
>
Hear, hear! One of these days I'll learn to read.
Nick
François Pinard writes:
> Nicolas Goaziou writes:
>> I'd rather pull you into writing a Texinfo back-end for the export
>> engine ;)
Well, Nicolas has been much helpful at getting me started on this one.
> I might aim Python.
Nicolas' works are so nicely done that it would be rather insane n
On Sat, Mar 31, 2012 at 9:24 PM, Stephen J. Barr wrote:
[...]
> | =var1= | this is the first var |
[...]
> However, pressing [TAB] after writing =var1= causes #ERROR to show up.
[...]
Just for the records. This issue has been resolved in the meantime with:
commit 8342fdb70aa28edbb7b0b18bf1f3
39 matches
Mail list logo
