Hi List, Hi Nicolas,
I (still) have a question about the parser and the yielded parse-tree:
- Circular List :: used for
- headline hierarchies (:parent attribute)
- plain-lists/items (:structure attribute)
- :CATEGORY attribute
- [somewhere else too??]
w.r.t. the :CATEGORY attri
Hi!
I just wanted to post a quick reminder that I finally found time to
debug the issue that caused tweets2org.py [1] to stop working:
Twitter changed their time-stamp format in the JSON files. I very
much do hate changing standards :-)
Now tweets2org.py is working flawlessly on my Twitter export
I believe I may have fixed the problem. I submitted two patches yesterday.
Hopefully they're formatted ok.
-deech
On Fri, Sep 13, 2013 at 7:27 PM, Suvayu Ali wrote:
> Hello Aditya,
>
> On Fri, Sep 13, 2013 at 06:42:13PM -0500, aditya siram wrote:
> > Hi all
> > I've made a couple of changes to t
Nicolas Goaziou gmail.com> writes:
>
> This was fixed in 8.1 release. You need to update Org.
>
> Regards,
>
Hi, updated to 8.1, but problem persists, does anyone know a way to solve this?
Thanks,
Simon.
Hi Nicolas,
2013-09-13 17:32 Nicolas Goaziou:
> If you're inserting the environment manually, Beamer export back-end
> will not be able to detect that a "fragile" option is required. In that
> case, you can also insert that option manually, by setting BEAMER_OPT
> property to fragile in the headli
On Sat, Sep 14, 2013 at 08:14:36AM -0500, aditya siram wrote:
> I believe I may have fixed the problem. I submitted two patches yesterday.
> Hopefully they're formatted ok.
I tried applying them, seemed to go fine. Note: I did not review the
patches.
A small pointer: I'm guessing you are using t
Dear all,
here is another problem that I have with reusing old Beamer
presentations (Org version 7) with the new exporter.
The manual says that "all frame's children become `block' environments".
Is there a way of reverting to the default behaviour of the old
exporter, which by default exported
Matt Price writes:
> Unfortunatey, I'm exporting to HTML (deck.js) not Beamer. I guess I
> still on't understand how to use beamer -- I tried it just now and it
> seemed to produce a very plain pdf, not a slideshow at all. sigh.
It may or may not have worked. I cannot tell from your comment.
Hello,
Christoph LANGE writes:
> Still I think the following sentence in the documentation (section 12.5)
> is easy to misunderstand:
>
> "`fragile' option is added automatically if it contains source code that
> uses any verbatim environment".
What would you suggest instead?
> I think it mean
Xebar Saram writes:
> Hi all and sorry about the complicated topic :)
>
> among the many many many things i use org for is to collect cooking recipes
> :)
>
> i have zero coding knowledge and my emacs understanding is limited :)
>
> what i basically wanted to ask is if anyone could show me a simp
On Sat, Sep 14, 2013 at 9:28 AM, Christoph LANGE
wrote:
> Dear all,
>
> here is another problem that I have with reusing old Beamer
> presentations (Org version 7) with the new exporter.
>
> The manual says that "all frame's children become `block' environments".
>
> Is there a way of reverting to
Nicolas Goaziou writes:
>> Should there be a pit-stop at #+END in the segment below.
> You can use `org-forward-element' to go there.
It makes no difference if I use `org-forward-element' or
`org-forward-linear-element'. The reason is clear if one examines the
parser output.
#+BEGIN and #+END
Christian Wittern writes:
> I am developing a mode derived from org for special editing and
> browsing purposes. I will add my own menu to the menubar and would
> like to remove the menus added by org, "Org" and "Tbl", in order not
> to confuse my users
Try this
(add-hook 'org-mode-hook
---
Fix a minor typo.
lisp/org-ctags.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/org-ctags.el b/lisp/org-ctags.el
index 98d47e5..9d8ed6c 100644
--- a/lisp/org-ctags.el
+++ b/lisp/org-ctags.el
@@ -131,7 +131,7 @@
;;
;; (progn
;; (message "-- rebuildin
Dear all,
having created a number of Beamer presentations with the old exporter
(Org version 7), I'm now working on the first Beamer presentation with
the new exporter.
Frames that contain an lstlisting environment are no longer made fragile
automatically. (Thus I'm not sure the documentation in
Hi Christoph and John,
I'll take an extreme view here. So apologies in advance.
On Sat, Sep 14, 2013 at 09:40:50AM -0500, John Hendy wrote:
> On Sat, Sep 14, 2013 at 9:28 AM, Christoph LANGE
> wrote:
> > Dear all,
> >
> > here is another problem that I have with reusing old Beamer
> > presentat
Thanks for this patch! I've just applied it.
For future patches it is good form to keep the first line of the commit
message <= 50 characters long (used to summarize the patch), the second
line should be blank, and all subsequent lines should be <=70 characters
long.
Thanks again.
aditya siram
aditya siram writes:
> Hi all
> I've made a couple of changes to the latest source tree but I can't seem to
> create patches because of some merges that happened subsequently.
First you'll need to rebase [1] your changes over the current head of
the git repository, then you can generate patches
aditya siram writes:
> Attached is a patch that fixes a bug with jumping from source block back to
> the Org file. The problem is that the current detangling behavior does not
> take the :padlline flag into account. This stopped.
>
> Hopefully this is helpful to others ...
> -deech
>
Hi deech,
Thanks for your feedback and your work on org-babel!
Oops, the maintain-point was a hold-over and isn't actually used in the
code. I'll remove it.
I will incorporate your suggestions.
However, regarding the cascading if statements, how would I use `cond` when
the predicates are `and`ed and when
org-src-fontify-natively doesn't fontify quoted LaTeX code like
#+BEGIN_LaTeX
#+END_LaTeX
the same as it does for LaTeX src blocks like
#+BEGIN_SRC latex
#+END_SRC
Why is that, and is there a way to get fontification for both ?
Julien.
I've included new versions of both patches with most of the changes you
suggested. I guess you'll apply the longer one when you've been notified by
the FSF?
Is this a one-time deal that covers future patches or do I have to do this
with every patch that's over 15 lines long?
Thanks!
-deech
On S
Hi Nicolas,
On Sat, Sep 14, 2013 at 12:29:00AM +0200, Nicolas Goaziou wrote:
> Hello,
>
> Carsten Dominik writes:
>
> > When the functions are done, please go ahead and commit them and bind
> > them to C-up/down.
>
> Done.
Do you think it would be nicer if org-forward-paragraph takes argument
On Sat, Sep 14, 2013 at 09:45:47AM -0600, Eric Schulte wrote:
>
> > Is there some way for me to issue a pull-request?
> >
>
> Pull requests are a github thing, not a git thing.
Well actually I think it is a Git thing. I believe it just says: my
changes are in the public branch , kindly pull fro
* Karl Voit wrote:
>
> Now tweets2org.py is working flawlessly on my Twitter export
> data-set and converts it to Org-mode format for my Memacs[2].
By coincidence a brand-new twitter module was added to Memacs[2]
today as well.
Many thanks to Ian Barton for this module which is using the Twitter
Hi,
I don't know if this has been linked to before on this mailing
list. At SciPy 2013, John Kitchin has made an amazing
demonstration of Org-mode as a tool for reproducible research.
Really amazing to watch.
http://www.youtube.com/watch?v=1-dUkyn_fZA
- Carsten
Hi,
With org-mode 8.0.7 (emacs 23.4.1), I have some problems to publish a
project.
I have this error : "Publishing file /home/xxx/site/org/index.org using
`org-publish-org-to-html'
find-buffer-visiting: Wrong type argument: stringp, (:base-directory
"~/site/org/" :base-extension "org" :publi
Suvayu Ali writes:
> On Sat, Sep 14, 2013 at 09:45:47AM -0600, Eric Schulte wrote:
>> Pull requests are a github thing, not a git thing.
>
> Well actually I think it is a Git thing. I believe it just says: my
> changes are in the public branch , kindly pull from there;
> eliminating the need to at
Hi Achim,
On Sat, Sep 14, 2013 at 08:12:57PM +0200, Achim Gratz wrote:
> Suvayu Ali writes:
> > On Sat, Sep 14, 2013 at 09:45:47AM -0600, Eric Schulte wrote:
> >> Pull requests are a github thing, not a git thing.
> >
> > Well actually I think it is a Git thing. I believe it just says: my
> > cha
Suvayu Ali writes:
> Isn't that two commands away:
>
> $ git remote add
> $ git pull
… and if you are a maintainer, then you'll have hundresds of remotes in
no time.
> If you use patches, you do lose committer information.
You might want to check that assumption. You can do it in many ways,
Hi all,
Org-mode uses two regex's to find headings, one from outline.el and one
defined internally and captures more information. I propose we stop using
the one from outline.el.
org-mode uses `org-back-to-heading` a lot to navigate point back to the
nearest heading.
This just delegates to `outli
On Sat, Sep 14, 2013 at 10:09:42PM +0200, Achim Gratz wrote:
> Suvayu Ali writes:
(I took the liberty to re-order the quoting below to clarify my argument.)
> > Isn't that two commands away:
> >
> > $ git remote add
> > $ git pull
>
> … and if you are a maintainer, then you'll have hundresd
Hi Aditya,
I do not support this idea.
1. sometimes Org functions are used in other modes, with a different value for
the outline regexp. WHile this will not work for many Org functions, it is
useful to have it work for some.
2. For just searching headings, it is efficient to use a regexp tha
On 9/14/13, Suvayu Ali wrote:
> (I took the liberty to re-order the quoting below to clarify my argument.)
I found this funny. :)
Samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. ANYBODY can get it.
Denmark: free
Suvayu Ali gmail.com> writes:
> I think it is unwise to keep coming up with ways to support semantically
> wrong behaviour just for the sake of backwards compatibility. This was
> changed with good reason and after a lot of discussions. If you
> continue on this path, you will have to keep main
On Sat, Sep 14, 2013 at 9:16 PM, James Harkins wrote:
> Suvayu Ali gmail.com> writes:
>
>> I think it is unwise to keep coming up with ways to support semantically
>> wrong behaviour just for the sake of backwards compatibility. This was
>> changed with good reason and after a lot of discussions
On 14.9.2013, at 19:16, Suvayu Ali wrote:
> Hi Nicolas,
>
> On Sat, Sep 14, 2013 at 12:29:00AM +0200, Nicolas Goaziou wrote:
>> Hello,
>>
>> Carsten Dominik writes:
>>
>>> When the functions are done, please go ahead and commit them and bind
>>> them to C-up/down.
>>
>> Done.
>
> Do you th
Applied, thanks.
- Carsten
On 14.9.2013, at 12:08, Gregor Zattler wrote:
> ---
> Fix a minor typo.
>
> lisp/org-ctags.el | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lisp/org-ctags.el b/lisp/org-ctags.el
> index 98d47e5..9d8ed6c 100644
> --- a/lisp/org-ctags.el
> ++
Hi Sebastien,
I don't think this patch is the right thing - is feels different from standard
Emacs behavior.
- Carsten
On 13.9.2013, at 12:02, Sebastien Vauban wrote:
> Hello,
>
> When moving with C-c C-v C-n (or p) from one code block to the next (or
> previous), it's much better if the cod
On 13.9.2013, at 10:01, Detlef Steuer wrote:
> Hi!
>
>> Hello,
>>
>> Rasmus writes:
>>
>>> So the question is should it be a default package?
>>>
>>> I think not. E.g. tabu isn't loaded. Amsmath isn't loaded if you
>>> generate a matrix.
>>
>> I think the "tabu" case (and longtable...) i
40 matches
Mail list logo
