Eric Schulte schulte.e...@gmail.com writes:
Rainer M Krug rai...@krugs.de writes:
Charles Berry ccbe...@ucsd.edu writes:
Eric Schulte schulte.eric at gmail.com writes:
Rainer M Krug Rainer at krugs.de writes:
The error is back:
You say back, was this error not present recently?
Rainer M Krug rai...@krugs.de writes:
Charles Berry ccbe...@ucsd.edu writes:
Eric Schulte schulte.eric at gmail.com writes:
Rainer M Krug Rainer at krugs.de writes:
The error is back:
You say back, was this error not present recently? If so could you
isolate the commit at which
Charles Berry ccbe...@ucsd.edu writes:
Eric Schulte schulte.eric at gmail.com writes:
Rainer M Krug Rainer at krugs.de writes:
The error is back:
You say back, was this error not present recently? If so could you
isolate the commit at which this error appeared?
The bug seems
Rainer M Krug rai...@krugs.de writes:
The error is back:
You say back, was this error not present recently? If so could you
isolate the commit at which this error appeared?
Thanks,
Eric
When one header in a subtree which has the header argument
:eval never
has the same name as in a
I reported it some time ago but couldn't reproduce it later, so I reported it
fixed. Now I realized that the 'reproducible example' did not show the error as
the header names were different. So I do not know if it is a new error, but I
can check on Friday.
Cheers,
Rainer
Envoyé de mon
Eric Schulte schulte.eric at gmail.com writes:
Rainer M Krug Rainer at krugs.de writes:
The error is back:
You say back, was this error not present recently? If so could you
isolate the commit at which this error appeared?
The bug seems to be in the use of
(org-link-search
