Re: Re: Bug: #+ATTR_LaTeX broken in LaTeX export [6.36trans (release_6.36.461.g798e)]

"Eric Schulte" <schulte.eric <at> gmail.com> writes:

[...]
>
> I'll add a function for clearing out tblname and tblfm lines, and insert
> it at the appropriate place in the export process.
>

done -- Eric

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode <at> gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [ANN] Org-babel integrated into Org-mode

Hi,

just to throw yet another idea into the discussion:

Execute source blocks only after the user confirmed it ("Do you know
what you are doing (Type y, n, !, or SPC)?").  ! and SPC will add the
current org file to the variables org-babel-trusted-files and
org-babel-trusted-permanently-files (also C-c C-v [ and C-u C-c C-v [
could do this).  The latter will be saved for future sessions.  And if
you also had a command to clean up this variable, removing
non-existing and/or old files from it...

This way the control of code execution by org-babel would be on the file
level instead of the global level.

Greetings,
	Stephan

Also sprach Eric Schulte:
> Dan Davison<dandavison7 <at> gmail.com>  writes:
>
>> "Eric Schulte"<schulte.eric <at> gmail.com>  writes:
>>
>>> Hi Carsten, Matt, Scott,
>>>
>>> Carsten Dominik<carsten.dominik <at> gmail.com>  writes:
>>>
> [...]
>>>> 1. A new variable org-turn-on-babel.  We can discuss the default.
>>>>     If it is nil, org-babel should not be loaded.

Re: [ANN] Org-babel integrated into Org-mode

Dan Davison <dandavison7 <at> gmail.com> writes:

> "Eric Schulte" <schulte.eric <at> gmail.com> writes:
>
>> Carsten Dominik <carsten.dominik <at> gmail.com> writes:
>>
>>> You main proposal was to make Org Babel an optional module.
>>> This will not solve the problem fully, I think, because we also
>>> don't want that people who turn it on automatically commit
>>> to potentially dangerous operations.  There is a lot of good stuff
>>> in Babel which has nothing to do with code evaluation.
>>>
>>> Here is what I propose (several items are similar to what Eric proposes)
>>>
>>> 1. A new variable org-turn-on-babel.  We can discuss the default.
>>>    If it is nil, org-babel should not be loaded.
>>>    A default of t would be fine with me if we implement other
>>>    measures listed below.
>>>
>>
>> This sounds like a good idea to me, and it should address Matt's desire
>> for enabling minimal Org-mode installs.  I would like this to default to
>> t, so that new users can try out Org-babel without overmuch effort.
>
> I'm not clear yet what the point of this is. Unless it is the load time
> which is the issue, what else is gained by this variable? In principle
> I'm also all for minimalism and modularity, but what does it actually
> mean here?
>
> If the effect of this variable is to not load org-babel code at all,

Re: [org-babel] Does org-babel needs some simplification?

Daniel Brunner <daniel <at> dbrunner.de> writes:

> I know, org-mode is a growing project and I really really like the
> org-babel features. But for me it is now not advisable any more to keep
> on the master branch. Today I spent several hours for finding the
> reasons why something is not working any more. And that is too much for
> a productive environment. 

I too run my production org-mode stuff from the master branch.  If you
pull and things break you can just step back to the commit you were at
before your pull with

$ git checkout ORIG_HEAD

All of your local commit changes should be available in the reflog so
you can go back to any recent point in time in your repository.

$ git reflog

will show a list of commits you have visited recently and you can return
to any one with a checkout of the SHA1 or by using the HEAD <at> {n} shortcut
-- just beware that HEAD <at> {n} changes everytime you move HEAD on your
repository.

Another method is to tag commits you know are good - so you can return
to them easily using whatever-name-you-like.

HTH,
Bernt

Re: [org-babel] Does org-babel needs some simplification?

Hi,

many thanks for the nice thoughts and posts.
To sum up, I think it might not be easy to remove parts of org-babel
since it is difficult to determine and a highly personal decision to
define what is important and what is unimportant.

Nevertheless Carten and Eric pointed out that the overhelming feature
set of org-babel, the fact that you could achive the same thing in
different ways and the missing of a "org-babel for dummies" might be a
problem for new org-babel users as well as for infrequent users.

Recently org-mode got his "org-mode for dummies" short manual. I guess
in the case of org-babel it might make more sense to create rather
typical examples for particular languages. This manuals could consist of
a typical example and of a template for this example which makes it easy
for beginners to fill in there own code and text.

Since Eric and the other org-babel and org-mode contributors are already
fully occupied with keeping org-babel and org-mode running, I would
suggest to collect a group of org-babel manual supporters. If possible
for each supported language one. This group could write up standard
situations for the particular language and maintain those manuscripts
whenever org-babel introduces some changes. In fact this group could
also serve as a kind of beta-testers for org-babel by trying on request
from e.g., Eric to compile there examples with the new org-babel
versions. I know there are some standard tests but I guess the do not go
that fare.

I guess, the manual maintainers do NOT have to be experts in both

Re: Exporting narrowed subtrees to HTML

Hi Bernt,

Bernt Hansen <bernt <at> norang.ca> writes:
>
> I am working in a deeply nested org file and have narrowed to subtree
> for the part of the file I'm working on which happens to start at
> heading level 5.
>
> I want to export this narrowed subtree to HTML but the first HTML
> heading level matches the file instead of starting from heading
> level 2.  This makes the resulting HTML output not as pretty as it could
> be.

If you select the subtree with C-c  <at>  (outline-mark-subtree), it should
export properly:

--8<---------------cut here---------------start------------->8---
<h1 class="title">Level 5 - Interesting stuff - narrow to subtree here</h1>

<div id="outline-container-1" class="outline-2">
<h2 id="sec-1">Level 6 </h2>
<div class="outline-text-2" id="text-1">

</div>

</div>

<div id="outline-container-2" class="outline-2">
<h2 id="sec-2">Another Level 6 </h2>
<div class="outline-text-2" id="text-2">

Re: [PATCH] resubmitted patch to contrib/lisp/org-mac-link-grabber.el

On Jun 30, 2010, at 7:32 AM, David Maus wrote:

> Anthony Lander wrote:
>> [1  <text/plain; US-ASCII (7bit)>]
>> This patch fixes an issue with opening AddressBook.app and
>> Together.app links.
>
> This is just a reply with the patch attached in a way the
> patchtracker[1] will catch it.

Applied, thanks.

- Carsten

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode <at> gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Bug: #+ATTR_LaTeX broken in LaTeX export [6.36trans (release_6.36.461.g798e)]

"Eric Schulte" <schulte.eric <at> gmail.com> writes:

Hi Eric,

> I've applied your patch.  I agree that a catchall cleanup function at
> the end of the export process is not solution.  Especially when it
> makes some perfectly valid constructs (e.g. nested blocks) impossible
> to export.

I can confirm that it works for me, now.

Thanks,
Tassilo

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode <at> gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Call org-remember on a "RE:" post raises error in gnus

Kane Dou wrote:
>When I call "org-remember" on a post like this: "O [ 40: Istvan ADAM ]
>Erroneous display when working on remote Unix machine".

>The backtrace("debug-on-entry" on "org-replace-escapes", no
>backtrace will occur if "org-remember" works normally):

Can you provide the backtrace for the error?

M-x toggle-debug-on-error RET

To get a backtrace without byte-code, just reload Org before provoking
the error (M-x org-reload RET).

HTH
  -- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena <at> jabber.org
Email..... dmaus <at> ictsoc.de

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode <at> gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [babel] Evaluating all source blocks in a document?

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode <at> gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode