Re: question about links, macros + org-publish and "parametrization"

[Martin Steffen]

>>>>> "Fraga," == Fraga, Eric  writes:

Fraga,> On Thursday, 30 May 2024 at 07:03, Martin Steffen wrote:
>> [...]  #+macro: target {{{source({{{year}}})}}}

Fraga,> So, the problem you are running into is that you cannot
Fraga,> evaluate a macro with arguments that require evaluating a
Fraga,> macro.  Unless you can change the order in which you
Fraga,> evaluate these macros, the only solution I can suggest is
Fraga,> that you define elisp macros.  See the info manual,
Fraga,> specifically the second example in the macro replacement
Fraga,> section.

thanks, fair enough, I look into the elisp-option. Martin




Fraga,> #+macro: complicated (eval ...)

Fraga,> -- : Eric S Fraga, with org release_9.6.19-1230-g407a55 in
Fraga,> Emacs 30.0.50

Re: question about links, macros + org-publish and "parametrization"

[Martin Steffen]

Hi,

maybe my email was premature. The combination of macros and links you
described is nice and useful for me (I did not much in the ways of
macros in org before). However, one aspect I am after seems not to work.

Your example was as follows, and it works:

--8<---cut here---start->8---
#+macro: link [[file:t.org][$1]]

#+macro: target {{{link($1)}}}

This is some text where I can look at {{{target(blah)}}}
--8<---cut here---end--->8---


There are 2 tweaks I had in mind in addition to your example, which
I can't get to work.

The first one is that the argument for the macro link should (also)
occur in the first part, a part of the link, not the text:

#+macro: source [[file:./$1/t.org][for the subdirectory  $1]]


That actually works, if one uses in the text

{{{target(bla)}}}

that's great, but it leaves me replacing in the text many occurrences of
"bla" across many files.

The second tweak is that "bla" is a macro as well (centrally defined).
something like the following (modifing your example)

--8<---cut here---start->8---
#+macro: year 24
#+macro: source [[file:./$1/t.org][for the year $1]]
#+macro: target {{{source({{{year}}})}}}
--8<---cut here---end--->8---

Then of I call the macros

1)   {{{source(24)}}}   : that works, $1 is replaced both times
  and the link points to file:./24/t.org

2) {{{source({{{year}}})}}}: that does not work 
3) {{{target}}}: that does not work either


In both cases 2) and 3), the result of the macro expansion is the following (I
export to markdown)


[for the year 24](./{{{year}}}/t.md)

-   [for the year 24](./{{{year}}}/t.md)

i.e, the argument  (intended to be 24) is properly replaced in ``text
part'' but not in the `` link'' part.


I don't know if I simply expect ``too much'' from the macro-expansion
facilities best, Martin




>>>>> "Martin" == Martin Steffen  writes:

>>>>> "Fraga," == Fraga, Eric  writes:

Martin> Fraga,> Hello,

Martin> Fraga,> I'm not entirely sure if I am missing something
Martin> but, in case

Martin> thanks, it was more that I was missing something. I tried to
Martin> combine links and macros in a naive ways (without much
Martin> studying the manual), so I thought perhaps nesting is not
Martin> possible (or there is another way).

Martin> Your suggestion solves my "problem" and makes the set-up a
Martin> bit more "parametric" and easier to adapt, without that one
Martin> forgets some bits, which is very nice.

Martin> best, Martin



Martin> Fraga,> it helps, macros can themselves invoke other
Martin> macros and Fraga,> macros can make use of [[target][desc]]
Martin> syntax directly.  Fraga,> Can you not build up a hierarchy
Martin> of macros that would Fraga,> achieve what you want, along
Martin> these lines:

Martin> Fraga,> #+macro: link [[file:t.org][$1]]

Martin> Fraga,> #+macro: target {{{link($1)}}}

Martin> Fraga,> This is some text where I can look at
Martin> {{{target(blah)}}}

Martin> Fraga,> HTH, eric

Martin> Fraga,> -- : Eric S Fraga, with org
Martin> release_9.6.19-1230-g407a55 in Fraga,> Emacs 30.0.50

Re: question about links, macros + org-publish and "parametrization"

[Martin Steffen]

> "Fraga," == Fraga, Eric  writes:

Fraga,> Hello,

Fraga,> I'm not entirely sure if I am missing something but, in case

thanks, it was more that I was missing something. I tried to combine
links and macros in a naive ways (without much studying the manual), so
I thought perhaps nesting is not possible (or there is another way).

Your suggestion solves my "problem" and makes the set-up a bit more
"parametric" and easier to adapt, without that one forgets some bits,
which is very nice.

best, Martin



Fraga,> it helps, macros can themselves invoke other macros and
Fraga,> macros can make use of [[target][desc]] syntax directly.
Fraga,> Can you not build up a hierarchy of macros that would
Fraga,> achieve what you want, along these lines:

Fraga,> #+macro: link [[file:t.org][$1]]

Fraga,> #+macro: target {{{link($1)}}}

Fraga,> This is some text where I can look at {{{target(blah)}}}

Fraga,> HTH, eric

Fraga,> -- : Eric S Fraga, with org release_9.6.19-1230-g407a55 in
Fraga,> Emacs 30.0.50

question about links, macros + org-publish and "parametrization"

[Martin Steffen]

Hi,

I got a question whether the following is possible, when using
org-publish. Concretely I generate with org-publish markdown-files (that
ultimately are turned to HTML), but I guess the question is not specific
for this choice of a ``publication-process''.'


The whole content consists of quite a number of files, and in particular
has quite many html-links, and the links change (each year, each
semester) and they change in ``systematic ways''


What has been  for instance

   https://www.gitpages.io/somelecture/fall23/exercises

will have to be changed for the next round to

   https://www.gitpages.io/somelecture/fall24/exercises

(and there are links for many things beside exercises, and also they
have to be changed analogously).


The way I make that smooth is I define

#LINK: exercises-web https://www.gitpages.io/somelecture/fall23/exercises


and then, When the semester comes, replace all occurrences of fall23 to
fall24. Even if there are quite a number of such link definitions (for
all kind of information), it's straightforward. It's systematically
organized, and if all the link definitions are centralized in some file
collectionoflinks.org or similar that is #INCLUDE:-ed into all the
other files that work with this links, then ``porting'' of the whole
set-up to a new semester is quite easy and robust.

So I am happy with that, but I wonder if I could make it even more
parametrized. Like


  combining macros with links


like that "fall23" is an argument to a macros, which then builds up a
link. But that does not to work in a naive way, like


#+MACRO: semester fall24
#+LINK: https://www.gitpages.io/somelecture/{{{semester}}}/exercises


since macros do replacement in "text" (not in those #+-"meta-commands").

I tried parametrized macros_

#+MACRO: parametricexercizes  https://www.gitpages.io/somelecture/$1/exercises


and that half-way works. I.e., if I do

   parametricexercizes(fall24)  (*)

it works in that it results in a page with a correct link, but that's
not quite what I want, for 2 reasons. Really useful would the
parametrization if one could do

  parametricexercizes(semester)

where semester is a macro, not a literal "fall24". The second reason is
that the use as in (*) is not really useful, what I am  really after is
something like

   [[parametricexercizes(fall24)][the exercises are here]]

and the combination of macros inside [[  ]] does not work either.



Maybe there are other ways to achieve ``parametrization'' (or maybe not,
I have not worked much with macros in Org), any ideas?

best, Martin

Re: Getting email from MS outlook into emacs

[Martin Steffen]

> "Ihor" == Ihor Radchenko  writes:

Ihor> alain.coch...@unistra.fr writes:

>> ... except when institution prohibits redirecting to another
>> email provider -- my case ...

Ihor> I would then simply use another email for most of the
Ihor> communication.  The institution email would then just be
Ihor> needed to communicate with institute-wide announcements.


That's a possibility I had indeed thought about, because also for me
it's forbidden to forward (automatically or not) stuff outwards from the
domain. I think it's not forbidden to "move" or sync emails to local
disk, as far as I can see, though I was not able to reasonably
automatize that (like with davmail, though that almost worked for a time
resp. partially...)

For institutional seasonal greetings or general announcements the
muddled outlook access would even be acceptable for me, who
cares. Unfortunately, there are many emails (from inside the
organization, a university) that are individual, relevant, and at times
urgent and requiring (re-)action and preferably efficient
organization, overview, and handling, but I cannot use alternative
email-addresses for that.



Martin






Ihor> -- Ihor Radchenko // yantar92, Org mode contributor, Learn
Ihor> more about Org mode at .  Support Org
Ihor> development at , or support my
Ihor> work at 

Re: Getting email from MS outlook into emacs

[Martin Steffen]

Hi,

not that I have a solution, but I would like to know one as well. Ever
since my organization moved to more or less exclusively Outlook, email
as working tool (for me) has constantly deteriorated. 2FA was one of the
last of the innovations, that was hard to "work with" as non
Microsoft/Outlook user (not Mac for me by emacs/linux). It's
increasingly frustrating, since it's a small drip-drip-drip downhill
experience. Once you get it sort of working again after it broke again,
they roll out a new "improvement" or feature after some time, which
perhaps adds some fancy wrinkles to the constellation of tremendous
things outlooks probably offers (I am just waiting for the
CHATGTP-plug-in that answers your emails for yourself...), but that
leaves people like me out in the rain, someone who just wants a
reliable, stable plain old email server which is widely compatible (even
if only backward compatible) and the leaves the choice of mailreader(s)q
to the user.

There seem to be features, that I don't want to get used to (seem like
auto-expire, emails vanish if read but not handled properly or
something), other emails I delete constantly re-awake (but in an expired
status, but still shown for me), other are undeletable (which leaves me
with a huge zombie-inbox), some are never shown in emacs-gnus.

So, I tried different approaches, all did not work (or stopped working
after a while, maybe after new "improvements" on the server side),
including davmail, procmail, and some other "sync" solutions if forgot,
but the main stumbling stone seemed 2FA ever since that was
introduced. I did not try mbsync though (maybe I will when I have time),
so I cannot really help.

But as said, I'd be likewise interested in directions for approaches. My
current goal is not to get access to the server enabled properly again,
but to get the emails (automatically) off the server, like 20+ years
ago, when internet and access to servers was unrealiable over "modem"
dial-ups. So back to the future, so to say.

best, Martin

Re: fancy TODO lists setup (emacs 29.1)

[Martin Steffen]

> I am unable to reproduce using both stable and main branches.

>> PS: My org version is Org mode version 9.5.2
>> (release_9.5.2-286-gd01235)

> This is not the latest version of Org. You can try to upgrade.



Thanks a lot. Seems like updating the org-setting did the trick already.

I got now

   Org mode version 9.7 pre (release_9.6.11-917)

and the todo's works basically unchange and as I am used to.

Re: An Org-mode-based blogging engine?

[Martin Steffen]

Hi,
> "Marcin" == Marcin Borkowski  writes:

Marcin> fully Org-mode-based workflow.  Ideally, I'd like to be able
Marcin> to do everything - including publishing the posts - from
Marcin> within Emacs.


I use webpage generation (including blogs) using Jekyll. Since I wanted
to stick to org, all is set-up in a way, that the ``content'' including
the blogs is done in org, and then do ``org-publish'' to generate stuff
as fit for consumption for jekyll and the workflow then continues from
there (basically just invoking jekyll to ``publish'' the stuff). jekyll
expects its content in md, but I feel more comfortable with org.

That leads to a two stage thing: first translate org to md (by an
appropriate org-publish set-up) and then generate the web-page from the
md-files. So it's not all org-workflow, but once it's set-up, it's
basically only org as far as content is concerned.


Fine points apply, as jekyll has a lot of moving parts and
configurations. And possible pictures and graphics etc. is also not ``in
org''- And actually, the org-files I am using have some jekyll-specific
md-prefix between

+begin_export markdown
+end_export

to tweak things for jekyll. But the org-part is easy, and for me it
works smooth. 


In a different response, HUGO was mentioned. I don't have experience
with HUGO, but it's probably comparable to jekyll.

Martin






Marcin> I know about things like "Org publish" and ox-hugo, though I
Marcin> never used them - and there are probably others - but I'm
Marcin> asking specifically about two things:

Marcin> A. other people's experiences with similar workflows, and
Marcin> B. tool/workflow recommendations.

Marcin> Here are my requirements, in no particular order.

Marcin> 1. I want the blog to be fully static HTML+CSS, with a tiny
Marcin> sprinkling of (my custom) JS.

Marcin> 2. I want to publish a whole set of HTML files from a single
Marcin> Org mode file.  I will need to preserve internal links (so
Marcin> that I can link to another headline and the result will be
Marcin> one post linking to another), and of course I will need
Marcin> external links.  The blog will live on some server I will
Marcin> have ssh access to, so for publishing it should be enough to
Marcin> scp some files somewhere.

Marcin> 3. I want to be able to fully customize the HTML produced.
Marcin> I want it to be as simple as possible (but see below).  I
Marcin> will also need it to be put in some kind of a template, so
Marcin> that every page will contain things like a header, footer
Marcin> and a sidebar.

Marcin> 4. I am going, though, to need some custom "blocks" - in
Marcin> HTML parlance, s and possibly also s.  I want to
Marcin> be able to mark them up somehow in my Org source and get
Marcin>  and .  Reusing existing
Marcin> markup (like _underline_, which I'm not going to use) is not
Marcin> enough - I will need more than a dozen of those custom
Marcin> classes.

Marcin> Any thought, suggestions, recommendations?

Marcin> -- Marcin Borkowski http://mbork.pl

Re: A dream?

[Martin Steffen]

Hi,

I also do some teaching, different courses, in earlier times lab
courses/project work, recently a quite large bachelor level course.

Some of the courses (like the ones mentioned) require keeping track of
many, many details (from my side), including administrational,
organizational stuff, open issues web-pages, instructions, exercizes,
deadlines, exams, grading etc).

To keep all of that under control, I use org. Also managing the masses
of students, I get a bunch of student assistents and graders that needs
also to be organized and, including a ``lead student assistent'' that
helps orchestrating the other student assistents (and the students
taking the course). For those cordinating tasks, keeping an overview, 
use org (though special tasks require special other solutions. For
instance, slides are done in latex, and ultimately, information, like
exam results, have to be uploaded into official administrative tool).


Some of the student assistants actually also use org. Some master level
students (not just the assistents) in another course use org as well for
things like documentation. For courses that involve more extensive
course work I use git and seem students appreciate that github honors
org as format for simple documentation and readmes etc.

That being said, it seems that among students I have in my courses,
markdown is more popular for such simple web-compatible documentations.
Also most student assistants use md, only some do org.


For really collaborative course works (like multiple students track
stuff on a joint project or all students need to have the same
org-setup), I never imposed org as format. Org is too flexible, perhaps,
as soon as one get's into it, everyone has one's own specific style to
use various features and it's tricky to get comfortable with someone
else's style (and _forcing_ all of them to adhere to one predescribed
style probably takes away what makes org great and makes it cumbersome.)

As a general observation in courses I gave where documentation (of
features, interfaces, plans, etc) was required (but where I did not
necessarily specified the exact tool or format), the best groups were
those that wrote the documentation not for me (``gee, the lecturer wants
some documentation, it seems mandatory, let's write up something for him
who cares anyway'') but those that realized that for a successful
collaboration and project they themselves profit from cleanly stating
and writing things.

And sometimes a well-organized Todo.txt-file does the job, as long as
the people feel it's the best solution for them. Though an org-file sure
would be superior.

So I think the tricky part will be to convince some of them, that doing
org is not some weird idiosyncrasy of the teacher, but may actually be
helpful. But that's hard. If you are grown up with eclipse or whatever
for hacking, and first have to learn yourself emacs, to learn yourself
org, to ultimately see the light, that org is good for todo lists in the
course, the semester is sure over...


For projects where something like a overall and common issue-tracker for
bugs etc was required for _all_ I normally also did not rely on org (or
do-what-you want-as-long-as-its-clean-and-helpful-for-you), but on
specialized issue-trackers, in the last course, github-issues .


best, Martin



> "Marko" == Marko Schuetz-Schmuck  writes:

Marko> Dear All,

Marko> I teach some software engineering courses and in each of them
Marko> students work on semester-long projects in teams. So far,
Marko> have let them choose their own tools for all the tasks
Marko> (implementation language, documentation tools,
Marko> etc.). Personally, I have been using org-mode for what feels
Marko> like forever. I was thinking that it would be nice to have
Marko> students use org-mode also for their project. I can see it
Marko> provide so many features that would benefit the projects:
Marko> easy links for e.g. traceability, tagging of requirements for
Marko> categorizing, responsible developer,..., of course todo
Marko> lists, priorities, progress tracking, rendering to web page,
Marko> PDF,...

Marko> Since these are students from a very technical background I
Marko> would hope they would be open to this.

Marko> Anyway, does anyone have any experience related to this,
Marko> maybe not specifically related to teaching, but software
Marko> engineering projects (with documentation of domain,
Marko> requirements, project approach, progress, references, source
Marko> code, testing, design, etc. etc. etc.)?

Marko> Best regards,

Marko> Marko

Re: [more absurd]

[Martin Steffen]

>writes:


> About the cultural thing... you seem to be a zero-counter (as I

I guess I am, by maybe have not been a zero-counter from the start, but
a 1-counter. I vaguely remember to have learnt (at school? beginning at
university?) that ``THE natural numbers'' (the ones Kronecker claimed to
have been created by God) start with $1$. There are referred to by
$\mathbb{N}$, and then there's also some versions, written
$\mathbb{N}_0$ (THE natural numbers ``extended'' by 0), they can be
handy too, sometimes.


>From a constructivistic point of view (and as a computer scientist, one
is obliged to have a constructivist view), for me 0 belongs to the most
natural way of defining natural numbers.

The fact that some theorems or facts are stated better this way or the
other is minor (as long as it's not that the vast majority of math on
Nats gets simpler without 0 (or with 0). One would also not work with
Nats starting at two like Nat ={2, 3,4,...}, for the extravagant
advantage to avoid stating clumsily a special-case condition ``a prime
number is a natural number larger or equal 2 and only divisible by 1 or
itself'' (if one thinks 1 and 0 are better not included in the prime
numbers, as most would do).

Constructing the nats from first principles seems to me a Nat is either
0, or the successor of a nat (succ n). Also for lists (and in complete
analogy): Lists are either empty () or built from cons-ing an element to
a list.

An analogous construction would of course also work using 1 as base
case resp. a one-element list as basic constructor. But it ``feels''
less natural for me in the meantime.


[talking about programming and data structures: while I think from a
practical (and aesthetic) point of view, lists should include the empty
list, and not start with lists of length 1 (likewise that functions
should be allowed to have a 0-length input parameter list), I found it
interesteding that _internally_, lists and similar data structures are
often usefully implemented with some ``sentinel'' node, i.e., the empty
lists is represented by some ``dummy cell'' in memory (not by
``nothing''), and a list of length n has additionally one such dummy
cell at the end, say, to make walking through the list, resp. checking
for the end more smooth and uniform, sometimes.]















> am, too): there, too, I think that "our" position isn't in any way
> "better" -- some theorems look better this way, some that way;
> some inductions are easier to start at 1, some at 0.

> Cheers -- t

Re: [more absurd]

[Martin Steffen]

>writes:

> On Mon, Jul 04, 2022 at 07:10:27AM +0200, Uwe Brauer wrote:

> [...]

>> That really su... (My use case only concerned numbers from 0-10).
>> 
>> So it boils down to the question: why isn't 0 considered as
>> natural numbers, as, according to the Peano axioms, it is?

> I don't know whether you're serious or making fun (Poe's Law and
> all that), but actually, Peano's axioms couldn't care less: as far
> as they are concerned, natural numbers could well start at 23 or
> something.

> Actually it seems to be some kind of "cultural question" whether
> mathematicians start counting at 0 or at 1; my observation is that
> they tend to agree across one faculty at one university.  I know
> positively one that tends to count from 1 (HU Berlin), another
> that counts from 0 (Freiburg), both in Germany.


In some sense that's defendable (that what could call natural numbers is
a cultural question or historical, like looking at what Peano did nor
did not define).

On the other hand, one normally does not just deals with the numbers as
such, one does something with it (like comparing them or calculating
with them). If one takes the reservoir of numbers (in decimal notation,
{0,1,2,3 .} indeed it is irrelelvant where to start, 0,1, or
23. Also if one does nothing else than comparing them (that would be
considering them as "ordinals", one has one single smallest number, and
again it's it's irrelevant if that's ``called'' nor notated $0$, "zero"
or "1", or "23".

Now, if one starts doing simple calculations (addition, multiplication),
the natural numbers including 0 is simply more "elegant" or ``richer''
than without. One has laws like n+0 = n, n*0=0 (one then says, 0 is a
neutral element wrt. +, there is terminology for all than, and it's
simply that N with 0 has nicer ``algebraic'' characteristics than
without. It's quite analogous to the choice between defining lists as to
include the empty list '() as a ``natural'' list, or insist on that
``natural'' lists must have 1 or more elements. 


> I once asked a maths prof and he said foundational folks (set
> theorists, math logicians -- that's the typical environment where
> you'd tend to stumble upon Peano) tend to favour starting at 0.


Foundational folks can elaborate on that analogy between lists and nats,
but as you say, in both cases they favor to include 0 to nats and the
empty list to lists (and there are more examples) and it's favored for
good reasons (at least to them).

best, Martin



> Historically, Peano himself seems to have been a one-counter:

>   "Peano's original formulation of the axioms used 1 instead of 0
> as the "first" natural number,[6] while the axioms in Formulario
> mathematico include zero."  as quoted in [1].

> Cheers

> [1] https://en.wikipedia.org/wiki/Peano_axioms -- t

Re: Depreciating TeX-style LaTeX fragments

[Martin Steffen]

Hi

to add my two cents. I am latex user of _many_ years (as user of emacs +
org), and I use it often for math-loaded texts.

I do use $ (I actually did not even know that \( \) is (supposed to be)
the new way  until I saw it generated by org.

As for $$ (or \[), I basically don't use it. I use
begin/end{displaymath}.

I don't care that it's a lot to type in, as I use an editor, that
assists me (said emacs ;-) resp. auc-tex mode).

I like the keybindings for environments there (and with the usual prefix
C-u C-x C-e, one can for instance turn a display-math into an equation,
should one decide later).

$$ I never used. The display-math simply looks nicer and is better
supported by auc-tex in that it uses standard indentation for
environments. For me it's likewise important that the text is properly
indented, and highlighted, so I can read the source file with easy,
while working on it.

Also \[ \] does proper indentation, but as said, I got used to C-x C-e
and that produces for me displaymath (probably it can be customized, but
I am happy with it as is).


Martin












> "Sébastien" == Sébastien Miquel  writes:

Sébastien> Hi,

Sébastien> With respect to readability, I only mean to point out
Sébastien> that the $…$ syntax is one less character, and that the
Sébastien> \(\) characters are quite overloaded.

>> this is a good opportunity to point out that $/$$ are very much
>> second class citizens in LaTeX now, no matter what you may see in
>> old documents.


Sébastien> The posts that you quote are 10 years old. As per [0]
Sébastien> (2020), there will be no LaTeX3. Nor is it only old
Sébastien> documents that use the $…$ syntax : looking for learning
Sébastien> ressources (see [1]), everything that I find uses
Sébastien> it. That includes The Not So Short Introduction to LaTeX
Sébastien> [2] (2021) and
Sébastien> https://en.wikibooks.org/wiki/LaTeX/Mathematics.

Sébastien> Although I have no evidence of this, my expectation is
Sébastien> that the majority of tex users use the $…$ syntax (it is
Sébastien> in fact widely used outside of tex: in most markdown
Sébastien> flavors and texmacs for example). I also expect that a
Sébastien> significant proportion of tex users are not aware of the
Sébastien> \(…\) syntax. I think here of users that are less tech
Sébastien> literate than most of this mailing list.

Sébastien> Regards,

Sébastien> [0]:
Sébastien> 
https://www.latex-project.org/publications/2020-FMi-TUB-tb128mitt-quovadis.pdf
Sébastien> [1]:
Sébastien> 
https://tex.stackexchange.com/questions/11/what-are-good-learning-resources-for-a-latex-beginner
Sébastien> [2]:
Sébastien> https://ctan.tetaneutral.net/info/lshort/english/lshort.pdf

Sébastien> -- Sébastien Miquel

What happened to ./contrib?

[Martin Steffen]

Hi,

I use org-mode, having cloned the git-version, pulling freshest versions
from time to time. Without a definite schedule when I do that I don't
know exactly when the change occured that I am asking here about.

Anyway, my  Org mode version is 9.4.6 (release_9.4.6-598-g604bfd @


Now: today I notices, some org-mode packages/files are missing. As said,
I don't know since when that was the case. In particular, emacs
initialization could no longer do

(require 'ox-extra)

since the file is gone. I looked around that not just file is no longer
part of the clone, but the hole

 contrib/lisp

directory (which is where that one was located) is gone.

Is there a reason for that, resp. is the functionality of ox-extra been
moved somewhere else?

Note that the documentation

  https://orgmode.org/worg/org-contrib/

(still) mentions currently a directory contrib, but in my latest pulled
version, it's gone (see also https://github.com/bzg/org-mode).

If course I can roll-back to an earlier revision or download one to get
back for instance ox-extra (which has a feature I rely on), but perhaps
there's something wrong.

Thanks, Martin

Re: First steps exporting to tex

[Martin Steffen]

> "Ypo" == Ypo   writes:

Ypo> Good morning

Ypo> After reading your interesting advices, I've decided to start
Ypo> my path through LaTeX. I have been some hours trying to start,
Ypo> with little result, but I hope that once established a
Ypo> *workflow* the results will come and the new invested time will
Ypo> be directed just to get better and better results.

Ypo> My doubts:

Ypo>  a. As first step for my workflow, it seems convenient to use a
Ypo> "template" with the LaTeX preambles. So maybe the many existing







Ypo> LaTeX templates can be used quickly with orgmode. I found
Ypo> several options and opinions. Which one is the best way?

I say my advice as a "LaTeX-first" person (i.e., I was familiar with
LaTeX before org was around. When I discovered org, which I found
useful in many ways, so I tried to familiarize myself also to find out
how I could make it useful in tandem with latex.

So, for me, stuff that works well in LaTeX, I did not port for myself to
org, things where org helps me to make better use of latex, I tried to
figure out.

For you, being familiar with org, but not (yet) with latex, you may
follow different patterns.

For the "preamble" of a latex document, the general setup that comes
_before_ \begin{document} and before any output is generated, I use
native latex using  instructions like

#+latex_header: \input{switches}
#+latex_header: \input{preamble}
#+latex_header: \input{style/style-common}
#+latex_header: \input{macros}

I often separate the preamble from macros. preamble.tex is (for me) the
file which contains loading of packages and classes (usepackage  etc,
and corresponding adapations or settings for that package). macros.tex is
things I define using \newcommand (or \def or \newenvironment or
similar)


As far controlling input is concerned, I also rely on latex-specific
setting (outside org, also outside emacs), things like environment
settings like $TEXINPUT, a path-specification, where one can control
where LaTeX finds (additional) stylefiles, outside of the standard
``load-path''.

Thus, I often try to avoid to use hardcoded things, like

>>> \input{~//export//template.tex}

I would use \input{template} (".tex" is not needed) and I make sure, the
templatex.tex file is included in the $TEXINPUTS-path. Typically, the
current directory "./"  should be included by default (and stuff from
the latex-installation is also routinely found)

BTW: also when working with pics (with includegraphs), there is a
variable (inside latex) that controls where to find figures. So, what I
typically would to is things like

\usepackage{graphicx}
\graphicspath{{./figures/}}   

That specifies that the pics for \includegrapic are found in a direcory
figures, and then I would use

\includegraphics[width=4cm]{jpgfigure}

not jpgfigure.jpg; \includegraphics can figure it out, if it's a PDF or
a jpg; it would also chose ps, if you don't use pdflatex, but latex (I
still prefer the xdvi-viewer as faster and more fluent to navigate, I
never like any PDF viewer when doing latex, only at the end, I generate
the PDF).


One can of course ``inline'' all that inside org (like doing a
\newcommand inside ``org'', it's just I prefer to keep all the stuff in
one (or more) latex files; for those parts I rely on latex (since org
does not bring much additional value to the table for the premable
stuff, at least for me)

Martin









Ypo> 1 #+SETUPFILE: template.setup -> doesn't seem the ideal way,
Ypo> because the template.setup file must be modified adding
Ypo> #+latex_class to each of the lines.  2 template.tex -> this
Ypo> could be added to the SETUPFILE: #+LATEX_HEADER:
Ypo> \input{template.tex}. But it seems to have no effect on the PDF
Ypo> output. BTW, I can't use emacs HOME path (~/) in the input
Ypo> header, like \input{~//export//template.tex}. This is my
Ypo> template.tex file content: \usepackage{fancyhdr}
Ypo> \thispagestyle{fancy}
Ypo> \lhead{\includegraphics[width=4cm]{jpg.jpg}} \rhead{Student
Ypo> Name: Name\\ Student ID: 1234\\ Course: IDB 601 (Fall 2020)} 3
Ypo> Another friend told me that .sty templates were the best way.
Ypo> 4 I see some people that create customized LaTeX classes and
Ypo> add the desired class to the orgmode buffer.  5 Also we can see
Ypo> this intricate transformation of a LaTeX template into
Ypo> orgmode. How to Migrate LaTeX Template into org-mode 6 ...

Ypo>  b. I think that in a good integration, every character shown
Ypo> on orgmode should be exported into the PDF output. For example
Ypo> "CENTRE LINE SYMBOL": ℄ How can this integration be done?

Ypo>  I have more doubts, but I will keep reading and trying to
Ypo> solve them

Ypo>  Best regards

Re: About exporting

[Martin Steffen]

> "Eric" == Eric S Fraga  writes:

Eric> On Tuesday, 30 Mar 2021 at 17:44, Juan Manuel Macías wrote:
>> However, *I would not recommend anyone to use LaTeX for
>> writing*. A light markup language is more comfortable and
>> efficient for me.

Eric> Totally agree!  Although, over the years, I have written many
Eric> papers in LaTeX directly, in the past decade I have
Eric> increasingly relied on org as the writing tool.  It imposes
Eric> much less friction on the creative process and, as you say, it
Eric> enables better management of the writing task.  And, as it
Eric> gives direct access to LaTeX when necessary, you lose nothing
Eric> by writing in org.

I would not go so far as not recommend latex (over org) for _anyone_ at
all. I for my part will stick with latex for a certain documents; for
others, org is better (has to do with the mentioned creative process,
and other advantages).


However, I write papers heavy in  math-notation (in the more theoretical
corners of conmputer science). There is a lot of math discplay (and I
like to rely heavily on macros etc).

For me, part of the preference of latex is the ratio between math and
similar things over ``text''. a blog-like text (not heavy on math), or a
note, or a wiki-like document etc, all that's great with org.

For math-typesetting, that's less of a ``creative flow of ideas
thing''. Of course, as having been mentioned, I can always escape to
latex inline or for displays etc. And I can also import my
macro-definitions etc (and I do that).

But actually, when typing, I think I am faster in latex. There are a
couple of features, I like (and my muscle-memory of my fingers rely in
them) in latex-modes of emacs.

Tab completion for environments and macros, remembering the last
environments I used, support of bibtex (like also completion or showing
the reference). Indentention of environments plus highlighting. And last
not least; if I ``compile'' the document (firing off latex, bibtex, or
index or whatever), the compilation runs in the background. As far as I
do that in org (exporting to pdf), it blocks emacs. Not that it's a
huge  delay even, at least for smaller documents, I hate that an editor
or some tool is slower than me, it gets on my nerves if the computer
slows me down. And there is a final thing which (for me) seem to work
better in latex-mode compared to org. That's jumping to the ``next
error'' with some key stroke. That's important,  LaTeX's own error
output it quite poor, but jumping to error locations is vital.


I would not be surprised if some of that is somehow supported by org as
well (for TeX), only I have not figured it out, or perhaps I was too
lazy to figure it out how. Too lazy because LateX mode works for me fine
even for challenging and long documents (where for simpler ones or where
the focus is not on typesetting org works).

Martin






Eric> And *tables*!  Enough said. :-)

Eric> But, as always, YMMV.

Eric> -- : Eric S Fraga via Emacs 28.0.50, Org
Eric> release_9.4.4-254-g37749c

Re: About exporting

[Martin Steffen]

> "autofrettage" == autofrettage   writes:

autofrettage> Hi,


autofrettage> Not even the most streamlined DTP-wysiwyg-program is

I agree. I did not want to imply that. 
autofrettage> safe from this.  Far from. I even doubt typewritten
autofrettage> documents can be written colla- boratively, without
autofrettage> someone messing things up.

Also that is common (I wrote many publications collaboratively with
latex. One can mess up at every level (from the line where a revision
merge conflict occurs, to latex incompatibilities (though that's not a
big problem resp. one can get that under control) up to notational,
linguistic or ``semantic'' incompatibilities (section 4 contradicts
content-wise what has been written is section 3). None of that can (or
should) be prevented by any form of tool. it depends on communicating
with each other, using one's brain, and a few other qualities.


As far as LaTeX vs. org is concerned (for producing readable documents
in varying degree of requirements as far as the complexity of document
is concerned and the typesetting quality), in my experience it's as
follows: of course everything that can be done by latex can be done with
org (trivially). As far as collaboration is concerned, if you get more
experienced with latex (and learn from mistakes and get better making
use of it), you will somehow rely on provided classed and other things
offered (and making good use of macros etc), and not messing it up,
knowing better than latex how it should looks like. That may including
writing class files yourself or style files (and sharing them with your
collaborators), but with experience you get more "disciplined" (if you
are willing to follow that discipline).


Though one can do the same in org (to disipline oneself to avoid messing
up collaboratively working on a shared document), I simply think it's
harder.

Both latex and org gives you freedom whatever you do (and you can use it
to mess it up; and as you send, also in a restrictive DTP or a harsh
straightjacket of producing "text" by filling out many small web-forms,
each free-form text at most 200 characters, like in a web-questionnaire,
you still can mess it up).

I enjoy the freedom that editing latex (and the support given by emacs)
for the same reason I enjoy the freedom of org (and the support given
many org-packages).


The difference is, in latex I don't want to explore the freedom I have
(like messing up things that styles prepared from me, or write
{\Large\textbf{Chapter 1: \hspace{4mm} Introduction}} instead of using
the command \chapter{Introduction}. And this experience of NOT using
parts of the freedom is shared with between experienced latex users
(especially those that collaborate in a good way with latex together on
shared documents) In org, getting experienced with org for me leads me
doing more and more creative things.  I have one or two colleagues, they
do completely different things than me or do it completely differntly,
and that's fine. But it's not a basis for using org for collaboratively
writing books. Of course it's doable, but requires more
(self-)discipline. I have also seen people I collaborate with that do in
LaTeX things like {\Large\textbf{Chapter 1: \hspace{4mm} Introduction}},
though this are either beginners (if they stick to this for them
established use of how to write LaTeX, makes a text-based collaboration
not useful for me On can still talk things through etc but not write
a common text :-))

In my experience, ith latex, it's possible to write text together for
well-intended people. Publishing houses tell you ``these are the classes
and style files (among perhaps others) that you _have_ to use, and also
do the following...''  (same possible for wisiwyg-editors, I assume),
and if you don't mess that up (like overwriting the defaults) you have a
chance to get a uniformely looking output (and on a halfway portable
platform, like a CTAN compatible latex installation). I cannot imagine
that publishers would prescibe ``this is the org-settings and features
you as author must to use to publish with us''.

Org (for the discussed usecase of exporting documents) is just a way to
produce LaTeX, latex takes care of portability and can assist with
uniformity and quality of type setting, but org intends (many) other
(useful) things.

Martin










autofrettage> There should be something like pilot licences for
autofrettage> using certain computer tools, not to speak about
autofrettage> programming, but let's not sink into squabbles about
autofrettage> that...

autofrettage> cheers Rasmus

Re: About exporting

[Martin Steffen]

Hi, here's my angle (which works for myself) how I use org-exporting in
connection with doing documents (I use in the meantime also org to
export as input for jekyll to produce HTML, but that's a different use,
the heavy lifting there is done in jekyll).


I am a LaTeX user since quite some time (also a bit TeX and texinfo)
ever since students. For LaTeX, I consider myself close to carrying a
black belt, maybe brown :-), for TeX and texi it's more dabbling (actually
for texinfo, I in the meantime use org and export to texinfo)

My (academic) environment and my field encourages use of LaTeX, that or
at least tolerates it; there are colleagues not to mention the
administration, who never would consider touching something
"unprofessional" like LaTeX, not mention org


Evern since I picked up org, I use org also to produce LaTeX. Often
diferent versions of Latex-src from the same org file. Sometimes LaTeX +
HTML side by side, sometimes ODT.

For ODT, it's often that someone forces me to ``it must be doc-file''
(or docx), because for some document and "doc-file" is synonymous.


The more the use-case for the document is proper typesetting /and
nothing else/, so the focus is on one single typeset output, the more I
simply work in LaTeX only. I have the feelinga it's faster, and the
fancy stuff (macros, enviorinments, styles, classes), I rely on LaTeX's
facilities anyway, even if I use org as pre-stage.

If I have a multi-purpose use-case, I often use org, or actually, it's a
mixure. Still the fancy stuff (typesetting specification, macros,
environments) is done in latex. By multi-purpose, I for instance
mean I do for some courses. The slides are in LaTeX, which means, beamer
mode,and org supports that reasonably. A different version of the
"slides" contains more text (sentences, expanations, etc). So I export a
different version (different export tags).

Still some portions of the overall document are native LaTeX. those are
typically included (not ``inlined''), often formulas and math
definitions, one reason being that editing LaTeX is faster in that case
than editing that in org.

And a third version could be HTML for webpages etc.  Of course one can
have conditional text in LaTeX as well, but org is quite good in that as
well. One can export latex to html, but generating it from org is
better.


There is one case where I do _NOT_ use org for such documents (though I
use org basically most things I do), and that is

 collaborative editing,

working together on a document (maybe shared by git), at least with a
document of some amount of complexity and typesetting requirement.

Even if I know that some colleagues use org (very few only, though), I
have the distinct feeling it gives too much headaches. Org would work
fine, being text, so revisioning is easy.

However, it's TOO flexible. I do quite complex documents with org
(exporting to latex), but I am not sure how sure to make it reliably
work when working together with one or more persons, and how much
``debugging'' and headache it would take.  I for instance like to test
out new packages, have the newest org. For LaTeX, that seems mostly
unproblematic, for org, not sure.

And then comes the personal habits: One great thing is that org is
flexible and one can make use of useful ``workflows'' or conventions
that profitable for oneself, and one gets used to it, one can adapt, and
then I have extra packages and adaptations. I can handle that (because I
adapt that myself), but it may conflict with other people's fiddlings.

Of course, in latex you can fiddle endlessly as well; even if one has
agreed on common macros and class files and conventios, one can easily
mess it up (typically for novices, who start changing layout or
typesetting, injecting manual spacing etc). But in LaTeX it seems more
under control, the purpose is to provide uniform typesetting of text
documents, it allows you to imposes "discipline" on the format (if you
are willing to stick to the agreed style files etc) Org, on the other
hand, is not about "uniform, classy output", it's not about
"discipline", it offers freedom and encourages playing around with, and
people who like to work with org _like_ to play around with it and to
stuff with it that others did not though of.

That's why I have not dared to write challenging (latex) documents with
org collaboratively (complex documents alone, yes, simple documents
jointly, but not all)
[
Martin














> "Ypo" == Ypo   writes:

Ypo> Hi

Ypo> After some years of using orgmode, and exporting using its
Ypo> defaults, I would like to take a quality leap and find a way of
Ypo> exporting for life. My options: LaTeX, ODT, HTML.

Ypo> LaTeX: I can see some masters here that make professional
Ypo> books, and I have some friends that publish scientific papers
Ypo> using LaTeX. But, it looks like a like a rabbit hole to me,
Ypo> since even the masters seem to have to modify the tex file
Ypo> d

Re: content management in emacs

[Martin Steffen]

> "Ian" == Ian Garmaise  writes:

Ian> Hi Bob,

Ian> How do you send mail to mailing lists with BBDB?  Do you use a

I am not sure about the question. If I send to an email list, it's an
address in BBDB. So I ``invoke'' BBDB (M-x bbdb) and give it the name of
the entry (say org-mode). That's analogous to send to a person: If you
remember the name (or part of the name), you find the entry, send then
compose an email ("m") on the entry.

Tab-completion may help.

If the question is: how do I send an email to all members of my chess
club or drinking buddies? If you have added some field to persons of
that circle (like "bridgeclub" or "drinkingbuddy", then you invoke bbdb
with that match, and then there is a possibility to send an email to
/all/ members of a matching list.


For phoning, I am not sure. I think there is (or was) a functionality to
initiate a call (probably with skype or ekiga or some such) but I never
used that.

Basically, for phoning, for me it's more like a rolodex, but a fast and
big one

Martin




Ian> templating tool?  Also, how do you start a phone call?

Ian> Ian

Ian>  Message: 28 Date: Sat, 27 Feb 2021 06:53:57 -1000 From: Bob
Ian> Newell  To: "emacs-orgmode"
Ian>  Subject: Re: contact management in
Ian> emacs Message-ID: 
Ian> Content-Type: text/plain

Ian>  I've used BBDB for years, and have tried org-contact, but it
Ian> didn't seem to scale to the now rather large size of my BBDB
Ian> database.

Ian>  I've looked at migrating to EBDB but as I have many custom
Ian> functions I haven't yet made the move.

Ian>  BBDB can do amazing things. I've mentioned some of them
Ian> before. Of course org links are supported, and in conjunction
Ian> with the 'gnorb' package, Gnus email can be associated with
Ian> BBDB entries in interesting ways.

Ian>  I use BBDB to easily maintain a slew of mailing lists. I also
Ian> have custom functions to set the input language mode for those
Ian> with whom I correspond in non-English languages. I even use
Ian> BBDB to initiate phone calls when I'm on my desktop computer.

Ian>  I hadn't thought to put BBDB under version control but that
Ian> would be very easy.

Ian>  However you don't need to get fancy right away. All the basics
Ian> are there. Like many things Emacs, it does take time to get
Ian> things set up the way you wish, but that time is well repaid
Ian> down the road a little.

Ian>  -- Bob Newell Honolulu, Hawai`i

Ian>  - Via GNU/Linux/Emacs/Gnus/BBDB

Ian>  End of Emacs-orgmode Digest, Vol 180, Issue 30
Ian> **

Ian> -- = Ian Garmaise Consultant Phorix Solutions Group
Ian> ia...@phorixsol.com Toronto cell: 416.432.2251 NYC:
Ian> 917.512.9535

Ian> https://www.linkedin.com/in/igarmaise/

Ian> http://www.PhorixSol.com

Re: contact management in emacs

[Martin Steffen]

> "Eric" == Eric S Fraga  writes:

Eric> How do you get these to appear?  Or is the "could" a wish?

It's ``automatic''. The entry of the person needs a field "anniversary",
if that's filled with a date in -mm-dd format, it's included
(perhaps one has to set a variable like ``show-bbdb-anniversaries''
and/or load a corresponding elisp-addition.)


Martin




Eric> thank you, eric -- : Eric S Fraga via Emacs 28.0.50, Org
Eric> release_9.4.4-231-gf46925

Re: contact management in emacs

[Martin Steffen]

I use bbdb (big-brother data base). I use it since a looong time
already, and amassed 15000 or so contracts. It does what I want, it's
text-based, so versioning is not a problem.

I think it can do vcard export (though when I used vcards is a long
time ago, I can't remember if that was smooth, I think it was with one
of my first smart phone, and I wanted to quick fill up the phone book
there with my ``emacs-managed'' contact data base.).

One can add used defined fields (where one can ``match'' all contacts
for some criterion, and send then ``bulk'' email.

Org is also bbdb-aware, insofar one can do those links: instead of
[[file:][yyy]] one can use [[bbdb:somecriterion]].

I don't know if it matches your needs, but I can't say bad things about
that bbdb-thing.

Martin

Re: preserving (zero-space) indenting in begin_src when exporting/publishing (to mark-down)

[Martin Steffen]

Great, thanks, That was it. It never occured to me that it's not
begin_src that I wanted, I just tried to tweak that one.

So, indeed:  #+begin_export markdown etc. is exactly what I need.

Thanks again.

Martin
> "Julius" == Julius Dittmar  writes:

Julius> Hi Martin,

Julius> if I understand correctly, you do not want to have a section
Julius> that quotes source code, but literal source code.

preserving (zero-space) indenting in begin_src when exporting/publishing (to mark-down)

[Martin Steffen]

Hi,

I have troubles to export (or publish) some orgfiles, which contain
``src'' snippets intended for markdown. The (for me) unwelcome behavior
is the same for org-export and org-publish, I guess, since it has the
same core reason.

The problem currently for me is for the markdown format. I have seen
similar behavior for other exports, though did not care since it for
those situations, it was/is ``good enough''. Now, however, I do some
export to md, to be used for Jekyll webpages, and it's no longer good
enough.

For concreteness sake: I got some section


#+begin_src markdown
---
layout: default
title: Some Title
description: Some information
---
#+end_src


which is exported to md literally, but with 4 leading spaces as
indentation, like

---
layout: default
title: Some Title
description: Some information
---

That's insofar unwelcome, as Jekyll wants those pieces of information
without indentation.

Alright, that's the situation, and the question is:

  is there a way to get rid of that

(during org-exporting/publishing, of course, not just post-processing
the md file).

This is what I tried so far. There are some variables one can tweak

1) org-src--preserve-indentation 
2) org-src-preserve-indentation 
3) org-edit-src-content-indentation

I set the 1) and 2) to "t" (also locally to the file to export). For 3),
the docs state it's about

  "Indentation for the content of a source code block."


So that sounded like it had something to do with my issue. Actually, the
original value was 2, and I set it to 0. There was no effect, the
indentation, when doing export, is still 4, as it was before setting
that to 0.


Any ideas? Thanks, Martin

Re: [O] orgmode beamer mode: BMCO does not export to latex any longer: ===> suspect identified: (ox-extras-activate '(ignore-headlines))

[Martin Steffen]

Hi,

one week ago I reported that export to latex/beamer refuses to export,
and the reason where it did not do it was, according to my email

BMCOL


(slides that contained that derailed the export terminally).

In the meantime, I found one line that, when removed, solves the
problem. In that sense, one might say, it's not BMCOL which is the
problem but the the combination. The problematic ``feature interaction''
is with the package

   (require 'ox-extra)

which in itself does not cause the damage, but if I add

   (ox-extras-activate '(ignore-headlines))


then that kills the export.  Note: there had been a time when that still
worked. 


PS: I tested it on the very latest git-pull (org-mode-version 9.1.6) and
emacs-24.3.1 (but I had similar problems for emacs-25, only that I did
not veryfy that it's the same line with ``ox-extra'' that causes the
trouble, but it's more than plausible).













>>>>> "Martin" == Martin Steffen  writes:

Martin> Thanks a lot, it may be that my emacs suffers some
Martin> ``package-overload'', i.e., maybe it's due to an
Martin> interference with some other lisp stuff I load.

Martin>  I just wanted to hear if it's known to be a current glitch
Martin> of the export-beamer thing, before I try to drill down
Martin> (especially since the priority is to make he slides compile
Martin> again rather than trouble-shooting. [I just escape to
Martin> native-latex for multi-cols for now]

Martin> When done with the presentation, I will try to narrow it
Martin> down, cutting down also on the amount of slides (because
Martin> currently is a long and complex thing, which I cannot expect
Martin> others to trawls for abnormalitiees ;-)

Martin> Martin






>>>>> "Eric" == Eric S Fraga  writes:

Eric> On Wednesday, 14 Feb 2018 at 10:39, Martin Steffen wrote:
>>> Hi,
>>> 
>>> since recently I have a problem with exporting org-beamer-mode,
>>> the culprit presumably

Eric> [...]

>>> It seems that the BMCOL is the culprit, org-beamer still export
>>> a complicated and long document (as it did before), but probably
>>> a recent update made it stumble over that particular element.

Eric> Works fine for me with org up to date from git.  Not sure what
Eric> to suggest.  What happens with emacs -Q and loading in org
Eric> with no customizations?

Eric> -- Eric S Fraga via Emacs 27.0.50, Org
Eric> release_9.1.6-118-g134243

Re: [O] orgmode beamer mode: BMCO does not export to latex any longer

[Martin Steffen]

Thanks a lot, it may be that my emacs suffers some ``package-overload'',
i.e., maybe it's due to an interference with some other lisp stuff I
load.

 I just wanted to hear if it's known to be a current glitch of the
 export-beamer thing, before I try to drill down (especially since the
 priority is to make he slides compile again rather than
 trouble-shooting. [I just escape to native-latex for multi-cols for
 now]

When done with the presentation, I will try to narrow it down, cutting
down also on the amount of slides (because currently is a long and
complex thing, which I cannot expect others to trawls for abnormalitiees
;-)

Martin






>>>>> "Eric" == Eric S Fraga  writes:

    Eric> On Wednesday, 14 Feb 2018 at 10:39, Martin Steffen wrote:
>> Hi,
>> 
>> since recently I have a problem with exporting org-beamer-mode,
>> the culprit presumably

Eric> [...]

>> It seems that the BMCOL is the culprit, org-beamer still export a
>> complicated and long document (as it did before), but probably a
>> recent update made it stumble over that particular element.

Eric> Works fine for me with org up to date from git.  Not sure what
Eric> to suggest.  What happens with emacs -Q and loading in org
Eric> with no customizations?

Eric> -- Eric S Fraga via Emacs 27.0.50, Org
Eric> release_9.1.6-118-g134243

[O] orgmode beamer mode: BMCO does not export to latex any longer

[Martin Steffen]

Hi, 

since recently I have a problem with exporting org-beamer-mode, the
culprit presumably

 BMCOL

It's org, in beamer mode. The mode still allows to turn some headers
into BMCOL (multiple colums) via some keybindings

``C-c C-b |'' (representing org-beamer-select-environment "|")

That results in lines like
--
*** Some text :B_block:BMCOL:
:PROPERTIES:
:BEAMER_col: 0.5
:END:
.

which is supposed to  be a block taking 50% of the slide's width.


So far so good (and as it used to be). 

Now, when /exporting/ the org-document to latex with 

 C-c C-e l b (l for latex, b for beamer-class)

the export peocedure trips over some error and 
  
   nothing is exported 

(the same occurs if I directly want to generated the PDF, and also if I
export the beamer-org document to a ``arcticle''-kind of style, so to
have a script). The message for the error reads like


--
[...]
org-babel-exp process tac at position 108835...
org-babel-exp process tac at position 109478...
org-beamer--format-block: Wrong type argument: number-or-marker-p, nil
-


It seems that the BMCOL is the culprit, org-beamer still export a
complicated and long document (as it did before), but probably a recent
update made it stumble over that particular element.


Any suggestion where to look?

thanks, Martin

PS: org-version="9.1.6"
emacs-version: GNU Emacs 24.3.1

Re: [O] Tab-completion no longer works?

[Martin Steffen]

> "Diego" == Diego Zamboni  writes:

Diego> Hi Martin,

Diego> I discovered this only yesterday, when I started using
Diego> org-mode from a git checkout and the shortcuts stopped
Diego> working. Turns out this functionality now has to be enabled
Diego> by loading the org-tempo library:
Diego> https://code.orgmode.org/bzg/org-mode/src/master/lisp/org-tempo.el. 
In

great. That did it. Thanks. Martin

[O] Tab-completion no longer works?

[Martin Steffen]

Hi, Since recently ---I can't remember exactly since when--- some
completion-feature I liked does not work any more.

By completion, I mean the expansion of 

   

Re: [O] external/central ``macro'' definitions (for instance link abbrev's)?

[Martin Steffen]

Eric S Fraga  ucl.ac.uk> writes:

> 
> On Saturday, 26 Mar 2016 at 11:43, Martin Steffen wrote:
> 
> [...]
> 
> > Now, the #+LINK mechanism works fine as such. But I want that it works 
> > for all used *.org files that constituted the overall document /without/
> > repeating the definition. Something like
> >
> > #+INCLUDE "definitions.org" 
> >
> > at the beginning of each file, so that if something changes, I need to
> > adapt only "definitions.org", not all files making use of that shared links.
> 
> Have you tried that?  Org supports include files:
> 
> #+include: "definitions.org"
> 
> (note :)
> 
> [[info:org#Include%20files][info:org#Include files]]
> 

yes, that's what I am using: org's support for including files. And 
the file content /is/ properly included. It seems mainly a mechanism for
"export" which is the main purpose.

I realize that my original post was perhaps unprecise. What I was looking 
after is this ``awareness'' of those definitions (using the #+INCLUDE
mechanism) /not just/ for export. I was missing it 

  /from within emacs itself/, 

i.e., from within org-mode.


I am using org-mode to document some software. For that, having those
``links''pointing to pieces of code is great. When generating HTML or other
formats, that allows to jumpt to it etc, that seems to work fine.


However, one way of browsing the documentation is /in emacs itself/ (using
org-mode). Following links seems to be done by C-c C-o
(``org-open-at-point''). The mechanism seems to be aware of links of the form

[[fileurl:file]] where fileurl is defined using the #+LINK mechanism.


However, it only seems to work if one /literally/ adds a #LINK-definition to
the file, resp. /all/ files where one wants that  (and refreshes the local
org-setting, after changing). But, as far as the org-internal browsing is
concerned (without exporting), I cannot easily follow those ``symbolically
defined'' links if I collect them in one specific central file. 

Note, if I export the orignal org-file as org-file, the newly exported
orgfile has the links expanded and then visiting it with emacs allows to
follow the links, but it's nice to have some fast browings while working
on/reading the original files.

Martin

[O] external/central ``macro'' definitions (for instance link abbrev's)?

[Martin Steffen]

Hi,

I like to achieve the following. I do a org-document which I separate
into different files (one per chapter or similar). They are all included 
into some "main.org".

In that setup, I'd like to use some centrally defined links, like


#+LINK: toollib  ../../src/lib

or similar, as an abbrev in hyperlinks like

[[toollib:somefile][somefile]] 



Now, the #+LINK mechanism works fine as such. But I want that it works 
for all used *.org files that constituted the overall document /without/
repeating the definition. Something like

#+INCLUDE "definitions.org" 

at the beginning of each file, so that if something changes, I need to
adapt only "definitions.org", not all files making use of that shared links.


Is there a way to achieve that? Thanks, Martin

[O] org keybinding "

[Martin Steffen]

Hi,

there seems to be a slight inconsistency wrt. exporting and keybinding.


I am doing LaTeX via org, more precisely latex/beamer. For latex-only
material, I use


#+BEGIN_EXPORT LATEX

#+END_EXPORT

[Side remark: that mark-up seems to be very recent, not very long ago, it
 had been 
  #+BEGIN_LATEX
  #+END_LATEX

]


Anyhow, for faster typing, I used the abbreviations provided, in that case
of LaTeX, the following tab-completion

  "

Re: [O] org latex/beamer math escape in a ``surrounding context'': $a$'s

[Martin Steffen]

> "John" == John Hendy  writes:

John> \(a\)s

John> Does that work for you?

yes, great (I was not aware that this is an alternative to the
dollar-dollar math, I only knew \[ )


Martin



John> John

>> 
>> Martin
>> 
>> 
>> 
>> 

[O] org latex/beamer math escape in a ``surrounding context'': $a$'s

[Martin Steffen]

Hi, I'd to have some math in beamer/latex. In LaTeX I'd write

   $a$'s

The a is the math, the apostroph-s is the surrounding text. Math-escape
works fine in org, but it seems the $ -- $ must be surrounded by blanks.
In the above example, exporting to latex/beamer does not give the desired
result. The immediately trailing "'s" get the $-signs interpreted
verbatimely. Same applies for other surrounding contexts like

   ``$a$''  $a$s 

but ($a$) and "$a$" do a math-escape. Is there a solution for the above (I
don't want to write  $a$ 's)? Or is there a rationale behind that, so I know
when to except an escape and when no?

Martin

[O] #+include: with ``adjustable'' path (separately defined, like macro expansion)

[Martin Steffen]

Hi,

I'd like to achieve something like the following (which does not work)

#+MACRO: custompath  ~/some/place/where/the/code/resides
#+include: "{{{custompath}}}src/example.code" 


Macro-expansion generally works, but not in those circumstances. I also
seens that there's the 

#+LINK: customurl

which conceptually does such macro expansion but it seems intended for
linking in stuff, not for "embedding" pieces of code.


Is there a way to achieve what I want, which I overlooked?
Thanks, Martin

Re: [O] org export customization: why do #+EXCLUDE_TAGS: settings have no effect?

[Martin Steffen]

Thanks,


For your small example (exporting to latex) I get

\begin{itemize}
\item H1 :private:
\item H2
\end{itemize}

(apart from the preamble etc).  What is also weird: If I add the
``standard'' vanilla template (via C-c C-e # beamer), then

- 1) some option settings like H:2  vs H:3 /are/ working.
- 2) variable org-export-headline-levels does not change


By "working" I mean: if I change the #+OPTIONS: H:2 to H:3, refresh the
emacs-buffer wrt. org's settings, and export the output (concretetely I
did beamer/latex). Now changing the section-level head /does change/ the
beamer-latex output the way I'd expect (i.e., it influences the
sectioning level).

What is strange though: the emacs-variable org-export-headline-levels
does not change when doing that, expect that I would have expected that
refreshing the buffer would do exactly that: update that variable and
thereby influencing the sectioning-levels:

-
org-export-headline-levels is a variable defined in `ox.el'.
Its value is 3
...
This option can also be set with the OPTIONS keyword,
e.g. "H:2".
-


I did not to comprehensive experiments which #+OPTIONS work or work
strangely, I just noticed that H:3 etc ``work'' (but I don't know why),
whereas the #EXCLUDE_TAGS do ``not work'' when refreshing the
buffer. For instance in that simple example you provided.

Martin





>>>>> "Nicolas" == Nicolas Goaziou  writes:

Nicolas> Hello,

Nicolas> Martin Steffen  writes:

>> Now: when I want to /customize/ that in the org-file itself, it
>> seems that's done by doing something like
>> 
>> 
>> #+EXCLUDE_TAGS: private

Nicolas> [...]

>> Anyhow: having such a specification in the org-file seems to have
>> /no effect/, even if I "refresh" the org-file, nor does it work
>> when I visit the file for the first time. It seems simply not to
>> affect the said variable "org-export-exclude-tags"

Nicolas> I cannot reproduce your issue. With the following buffer

Nicolas>   #+EXCLUDE_TAGS: private * H1 :private: * H2

Nicolas> I get

Nicolas>   1 H2 

Nicolas> when I export to, e.g., UTF-8.


Nicolas> Regards,

Nicolas> -- Nicolas Goaziou

Re: [O] unfortunate "feature interaction" of org-export and emacs-latex-auctex mode

[Martin Steffen]

> "Marcin" == Marcin Borkowski  writes:


Marcin> Note: this is a terrible hack, so use it your own risk, only
Marcin> if there's no sane alternative etc.


Works for me, thanks (and for the suggestions of the others in the
thread. Martin


Marcin> #+BEGIN_COMMENT
Marcin> 
%
Marcin> %%% Local Variables: %%% mode: org %%% End:
Marcin> #+END_COMMENT #+BEGIN_LATEX
Marcin> 
%
Marcin> %%% Local Variables: %%% mode: latex %%% TeX-master: t %%%
Marcin> End: #+END_LATEX

>> Martin

Marcin> Hth,

Marcin> -- Marcin Borkowski
Marcin> http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of
Marcin> Mathematics and Computer Science Adam Mickiewicz University

[O] unfortunate "feature interaction" of org-export and emacs-latex-auctex mode

[Martin Steffen]

Hi,

Perhaps it's not really a "fault" of org (nor of auctex), but both
things interact unfortunate. 

The reason is: when I export org to LaTeX, and I visit the latex file
afterwards, I want that auctex/emacs is instructed about some facts. Thus I
like to have some lines such as

%%% Local Variables: 
%%% mode: latex
%%% TeX-master: t
%%% End: 

at the end of the latex file. Org allows that, in that I add the
"LATEX-only" export at the end of the org-file

#+BEGIN_LATEX
%
%%% Local Variables: 
%%% mode: latex
%%% TeX-master: t
%%% End: 
#+END_LATEX


Doing that produces the desired lines at the end of the generated latex, and
if I visit the latex file, emacs/auctex is instructed according to my wishes.


Now the problem: If I refresh the /org/ file, emacs/org thinks that actually
the file is a latex file (due to the line "mode: latex") and switches from
org-mode to latex-mode.


It's a minor thing, obviously, but I just wonder if there's an easy workaround.

Martin
 

[O] org export customization: why do #+EXCLUDE_TAGS: settings have no effect?

[Martin Steffen]

Hi,

I want selective export in org (for instance, exporting to beamer/latex, and
html etc). I seem to understand the "theory" but it seems not really to work
for me.


what _works_ is as follows: I set directly a corresponding variable, in
particular, for instance, set it "hard" to

(setq org-export-exclude-tags '("noexport" "private" "handout")


"noexport" is the original value, but I want to keep trees tagged as
"private" and as "handout" out of for instance the slides.

Now that seems to work.

Now: when I want to /customize/ that in the org-file itself, it seems that's
done by doing something like


#+EXCLUDE_TAGS: private


(In (older?) versions, I also found #+EXPORT_EXCLUDE_TAGS). 


Anyhow: having such a specification in the org-file seems to have /no
effect/, even if I "refresh" the org-file, nor does it work when I visit the
file for the first time. It seems simply not to affect the said variable
"org-export-exclude-tags"


--

I use a pretty up-to-date org version pulled from git-hub (org-version
8.3.2, emacs-version 24.3.1)

Martin

Re: [O] org-mode 3.5.1 emacs 24: invalid-functon 41

[Martin Steffen]

Hi Nicolas, and all.

I recently answered to a prior suggestion concerning the cause of a
problem (see below), basically I could not confirm the cause of the
error. In the meantime, I had the same problem (on different computer),
again with the newest org-mode with the same symptoms (org-mode
basically broken, with constant ``invalid function 41'' message).


I applied the suggested patch, and it made the symptoms go away. So it
seems that it cause of the error was located.

Thanks, Martin


>>>>> "Martin" == Martin Steffen  writes:

Martin> Hi,

Martin> thanks for the info. I tried to reproduce the error but
Martin> failed, which means, in the meantime org 3.5.1 works.

Martin> Note, however, that it's no longer the same
Martin> git-reversion. When I first stumbled upon it, it was
Martin> org-version 3.5.1 and the then latest pull from the
Martin> git-server. Since it basically made all of org unsusable
Martin> ("RETURN" did not work any longer), I decided to ``go back
Martin> in time'' and git-pulled an earlier version (namely the one
Martin> git-labeled "release 3.5").

Martin> Now, in order to reproduce the error (and try the patch), I
Martin> pulled the now latest one, and the ``41-error'' does _not_
Martin> show up. I also applied to small patch (because the 2 lines
Martin> you pointed at do appear in the org-element.el file), but
Martin> that does not lead to an immediately visible change (but as
Martin> said, the error was gone already).

Martin> Unfortunately, I don't know which exact revision it was that
Martin> showed that problem ---I think in the meantime I did not
Martin> also update emacs itself---, but if it disappeared in the
Martin> now latest version, I am content as well.


Martin> Thanks, Martin


Nicolas> Hello,

Nicolas> Martin Steffen  writes:

>>> org-element--set-regexps: Invalid function: 41

Nicolas> 41 is ?\) character. I think the problem lies in this
Nicolas> snippet from `org-element--set-regexps'

Nicolas> (case org-plain-list-ordered-item-terminator (?\) ")")
Nicolas> (?. "\\.") (otherwise "[.)]"))  ^^^




Nicolas> Could you try the following patch?

Nicolas> diff --git a/lisp/org-element.el b/lisp/org-element.el
Nicolas> index 8f41ab2..7b95e0d 100644 --- a/lisp/org-element.el +++
Nicolas> b/lisp/org-element.el @@ -177,8 +177,11 @@ specially in
Nicolas> `org-element--object-lex'.")  ;; Clock lines.
Nicolas> (regexp-quote org-clock-string) "\\|" ;; Lists.  - (let
Nicolas> ((term (case org-plain-list-ordered-item-terminator - (?\)
Nicolas> ")") (?. "\\.") (otherwise "[.)]")))  + (let ((term (if
Nicolas> (characterp + org-plain-list-ordered-item-terminator) +
Nicolas> (char-to-string + org-plain-list-ordered-item-terminator) +
Nicolas> "[.)]"))  (alpha (and org-list-allow-alphabetical
Nicolas> "\\|[A-Za-z]"))) (concat "\\(?:[-+*]\\|\\(?:[0-9]+" alpha
Nicolas> "\\)" term "\\)" "\\(?:[ \t]\\|$\\)"))


Nicolas> Regards,

Nicolas> -- Nicolas Goaziou

Re: [O] org-mode 3.5.1 emacs 24: invalid-functon 41

[Martin Steffen]

Hi,

thanks for the info. I tried to reproduce the error but failed, which
means, in the meantime org 3.5.1  works. 

Note, however, that it's no longer the same git-reversion. When I first
stumbled upon it, it was org-version 3.5.1 and the then latest pull from
the git-server. Since it basically made all of org unsusable ("RETURN"
did not work any longer), I decided to ``go back in time'' and
git-pulled an earlier version (namely the one git-labeled "release
3.5").

Now, in order to reproduce the error (and try the patch), I pulled the
now latest one, and the ``41-error'' does _not_ show up. I also applied
to small patch (because the 2 lines you pointed at do appear in the
org-element.el file), but that does not lead to an immediately visible
change (but as said, the error was gone already).

Unfortunately, I don't know which exact revision it was that showed that
problem ---I think in the meantime I did not also update emacs
itself---, but if it disappeared in the now latest version, I am content
as well.


Thanks, Martin


Nicolas> Hello,

Nicolas> Martin Steffen  writes:

>> org-element--set-regexps: Invalid function: 41

Nicolas> 41 is ?\) character. I think the problem lies in this
Nicolas> snippet from `org-element--set-regexps'

Nicolas>   (case org-plain-list-ordered-item-terminator (?\) ")")
Nicolas> (?. "\\.") (otherwise "[.)]"))  ^^^




Nicolas> Could you try the following patch?

Nicolas> diff --git a/lisp/org-element.el b/lisp/org-element.el
Nicolas> index 8f41ab2..7b95e0d 100644 --- a/lisp/org-element.el +++
Nicolas> b/lisp/org-element.el @@ -177,8 +177,11 @@ specially in
Nicolas> `org-element--object-lex'.")  ;; Clock lines.
Nicolas> (regexp-quote org-clock-string) "\\|" ;; Lists.  - (let
Nicolas> ((term (case org-plain-list-ordered-item-terminator - (?\)
Nicolas> ")") (?. "\\.") (otherwise "[.)]")))  + (let ((term (if
Nicolas> (characterp + org-plain-list-ordered-item-terminator) +
Nicolas> (char-to-string + org-plain-list-ordered-item-terminator) +
Nicolas> "[.)]"))  (alpha (and org-list-allow-alphabetical
Nicolas> "\\|[A-Za-z]"))) (concat "\\(?:[-+*]\\|\\(?:[0-9]+" alpha
Nicolas> "\\)" term "\\)" "\\(?:[ \t]\\|$\\)"))


Nicolas> Regards,

Nicolas> -- Nicolas Goaziou

Re: [O] org-mode 3.5.1 emacs 24: invalid-functon 41

[Martin Steffen]

Bastien  gnu.org> writes:

> 
> Hi Martin,
> 
> Martin Steffen  ifi.uio.no> writes:
> 
> > (setq load-path (cons "~/gnu/emacs/24/lisp/org/lisp" load-path))
> > (setq load-path (cons "~/gnu/emacs/24/lisp/org/contrib/lisp" load-path))
> > (add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode))
> 
> After you start Emacs in this minimal mode, can you call
> 
> M-x org-reload RET
> M-x org-version RET
> 
> and report the value?
> 
> Also, grep'ing through your ~/gnu/emacs/ folder to find "41" somewhere
> might help.
> 



thanks for the feedback. What I did in the meantime: I checked out an older
version (I git-checked out a tag  "release_8.3") which made the troubles go
away. 


Now, to re-produce the error: I went back to the last revision which 
showed for me the error and started the minimal emacs (--no-init-file) again.

After starting emacs in the above mentioned  minimal mode (as you proposed),
I called M-x org-reload. That gives the output (1) below.

Org-version gives:


Org-mode version 8.3.1 (release_8.3.1-117-gc98729 @
/ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/)




The grep'ing of the directory does not reveal much. There's some occurences
of "41" in some time stamps or in hex-codes, but not much that seems to
relate to a "function 41". Note also: since I invoke emacs with
"no-init-file" and since my personally extended directories are not entered
to the load-path (apart from the org-subdir), none of the stuff I normally
load from there should play a role in the problem.

In general, I had the impression it's a rather fundamental bug: I disallows
me to type "RETURN" in an org file. More precisely, I cannot type
"RETURN" in "org-mode". If I do, I get the error message

invalid function 41

and the return is not executed (insofar that no new line is added but an
error raised). Due to 
that, org-mode for me in that version is ``broken'' as a cannot enter a new
line at all (except I can "cut-and-paste" a new line  or similar) which is
why I checked-out the previous tag.

.
Martin


-- (1) ---

Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-comint...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-core...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-emacs-lisp...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-eval...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-exp...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-keys...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-lob...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-ref...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-table...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/ob-tangle...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-compat...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-entities...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-faces...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-footnote...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-list...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-macro...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-macs...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-pcomplete...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-src...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-w3m...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org-version.el
(source)...done
Loading /ifi/asgard/a01/msteffen/gnu/emacs/24/lisp/org/lisp/org.el (source)...
Problems while trying to load feature `org-bbdb'
Problems while trying to load feature `org-bibtex'
Problems while trying to load feature `org-docview'
Problems while trying to load feature `org-gnus'
Problems while trying to load feature `org-info'
Problems while trying to load feature `org-irc'
Problems while trying to load feature `org-mhe'
Problems while trying to load feature `org-rmail'
org-element--set-regexps: Invalid function: 41
Quit
Mark set

[O] org-mode 3.5.1 @ emacs 24: invalid-functon 41

[Martin Steffen]

Hi,

I have recently git-pulled the latest org-mode (and make-compiled it).
Since the upgrade, org is basically broken. If I visit a file, emacs answers
with invalid-function 41 (I have debug-on-error to "t", but it does not give
much info where it chokes).

I have now org-version 3.5.1. Before the upgrade, it was, I assume some
3.5.0 (maybe 3.5.0h, and that worked). 

emacs-version: 24.5.2


If I use emacs 23.1, the problem goes away.

To avoid interference with too many loaded packages (including org-features).
I started emacs with

   emacs --no-init-file

and eval'ed just the following 3 lines


(setq load-path (cons "~/gnu/emacs/24/lisp/org/lisp" load-path))
(setq load-path (cons "~/gnu/emacs/24/lisp/org/contrib/lisp" load-path))
(add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode))


Here's some other errors in the *Messages* buffer:




Problems while trying to load feature `org-bbdb'
Problems while trying to load feature `org-bibtex'
Problems while trying to load feature `org-docview'
Problems while trying to load feature `org-gnus'
Problems while trying to load feature `org-info'
Problems while trying to load feature `org-irc'
Problems while trying to load feature `org-mhe'
Problems while trying to load feature `org-rmail'
File mode specification error: (invalid-function 41)

[O] Bug: org-clock-in missing + agenda start up error [7.9.2 (release_7.9.2-567-g854ddf-git @ org-loaddefs.el can not be found!)]

[Martin Steffen]

Hi,

since some time, I got an number of problems with org-mode, e.g., error
messages when starting the agenda the first time.  I don't know whether
it's related to another error, but I suspect so, so I mention both.


  1) clockin in no longer works:

  I can no longer clock-in, when typing, the message is


   Function definition is void: org-clock-in

(same for clock-out)


   2) agenda start up error:

When I try to invoke the agenda the _first_ time emacs throws an
error. The error trace/call stack starts with

 call-interactively(org-agenda nil nil)


and the error occurs at 


  Debugger entered--Lisp error: (void-function org-element-context)
(org-element-context)


If I try to invoke the agenda the second time, the error
disappear, even if the agende is not "formatted" correctly. 
If I then invoke the agenda the third time, it looks ok.

As said, I don't know whether the bumpy agenda start-up causes the
clock-error or is otherwise related, but these errors appear not some
time, and seemed to have appeared around the same time. 


PS: I use pretty much the newest org-mode available via git, and my
emacs is 24.2.3 (but the same appears also at some emacs-23, which I
tried).


Chees, Martin










Emacs  : GNU Emacs 24.2.3 (x86_64-unknown-linux-gnu, GTK+ Version 2.10.4)
 of 2012-10-29 on xxx.xxx.xxx.xxx
Package: Org-mode version 7.9.2 (release_7.9.2-567-g854ddf-git @ 
org-loaddefs.el can not be found!)

current state:
==
(setq
 org-export-preprocess-before-selecting-backend-code-hook 
'(org-beamer-select-beamer-code)
 org-tab-first-hook '(org-hide-block-toggle-maybe 
org-src-native-tab-command-maybe
  org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
 org-track-remove-package t
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-export-preprocess-before-normalizing-links-hook 
'(org-remove-file-link-modifiers)
 org-log-done 'note
 org-confirm-shell-link-function 'yes-or-no-p
 org-track-compile-sources nil
 org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc
   org-beamer-auto-fragile-frames
   org-beamer-place-default-actions-for-lists)
 org-todo-setup-filter-hook '(org-choose-setup-filter)
 org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
 org-agenda-custom-commands '(("f" occur-tree "FINISH"))
 org-todo-get-default-hook '(org-choose-get-default-mark)
 org-default-notes-file "~/priv/org/notes.org"
 org-export-define-heading-targets-headline-hook 
'(org-wikinodes-set-wiki-targets-during-export)
 org-todo-keyword-faces '(("TODO" :foreground "orange" :weight bold) 
("UNDERWAY" . org-warning)
  ("DEFERRED" . shadow) ("DELEGATED" :foreground 
"yellow" :weight bold)
  ("PENDING" :foreground "brown" shadow) ("DONE" 
:foreground "green")
  ("DORMANT" :foreground "grey")
  ("CANCELLED" :foreground "grey" :weight bold))
 org-agenda-include-diary t
 org-drawers '("PROPERTIES" "LOGBOOK" "CLOCK" "HIDINGDRAWER" "WEGGEKLAPPT")
 org-after-todo-state-change-hook '(org-clock-out-if-current org-checklist)
 org-track-directory "~/Downloads/"
 org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-font-lock-set-keywords-hook '(org-wikinodes-add-to-font-lock-keywords)
 org-trigger-hook '(org-depend-trigger-todo org-choose-keep-sensible)
 org-mode-hook '(org-drill-add-cloze-fontification turn-on-font-lock
 (lambda nil
  (org-add-hook (quote change-major-mode-hook) (quote 
org-show-block-all)
   (quote append) (quote local))
  )
 (lambda nil
  (org-add-hook (quote change-major-mode-hook) (quote 
org-babel-show-result-all)
   (quote append) (quote local))
  )
 org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-refile-targets '((org-agenda-files :maxlevel . 3) (org-agenda-files :tag . 
""))
 org-clock-persist t
 org-ctrl-c-ctrl-c-hook '(org-wikinodes-clear-cache-when-on-target 
org-babel-hash-at-point
  org-babel-execute-safely-maybe)
 org-directory "~/priv/org"
 org-enforce-todo-dependencies t
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-hide-inline-tasks org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-export-lat

[Orgmode] org-timeline and diary/calendar

[Martin Steffen]

Hi,

is there a way to include diary entries (i.e., entries in an
emacs-calendar file) into the org timeline?


I have set 

   (setq org-agenda-include-diary t)


which incluse the diary to the agenda-day view; but it seems that in the
timeline it is not included.


Thanks, Martin




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

[Orgmode] ``repairing'' time logging/clocks

[Martin Steffen]

Hi,

I got a question about time logging. Sometimes I forget/had forgotten to
clock-out. If I clock out correctly, it entries look for instance as


  CLOCK: [2010-04-24 Sat 06:56]--[2010-04-24 Sat 06:58] =>  0:02


To repair dangling clocks, one can use, it seems, 

  M-x org-resolve-clocks

where one has a number of options (keep, cancel...). However, in my
orgfile, I have a quite number of time-log entries of the form



  CLOCK: [2010-04-24 Sat 06:56]--[2010-04-24 Sat 06:58](***)


i.e., the sum is missing. The reason why I have those is because I
repaired non-finished clocks 

CLOCK: [2010-04-24 Sat 06:56]--


by just manually adding the end-time. That seemed to work in that the
sum will appear in summary clock tables.  However, entires of the form
(***) are considered "dangling" and since recently org prompts me to do
something about it, i.e., resolve them.

 Is there a possibility to _automatically_ add the number of minutes and
 complete the enty (***)  to one where the => is added correctly?


Alternatively: if I want to not repair my file right now, can I switch
of that each time I want to clock in, I am prompted to do something
about the old clocks?

Cheers, Martin


PS: I use org-version 6.35g and emacs 23.1.94
















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