Re: [External] : Re: how to investigate? org-element-cache Unregistered buffer modifications detected

[Ihor Radchenko]

Daniel Ortmann  writes:

> ... I rebuild at least once per day.
> My current org-mode version is:
> Org mode version 9.5.4 (release_9.5.4-596-gaa5bc2 @
> /home/dortmann/src/git-org-mode/lisp/)
>
> A bit more information may help?
>
>   * 1.2MB org-mode file
>   * received a stubborn parse error after today's build; could not load
> my org file; the file location looked fine
>   * partitioned the large file into smaller files
>   * ... was able to load each of those smaller files
>   * afterwards, without any changes, I was able to load the full file
> without the 'parse error'

That was related to another bug that was introduced in
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f77800c68b69f770886b9c103a101550ec530896
and then fixed in
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=d788fe99272d3563ff88e872bf337b8c198c7c7d

I now pushed another change that will prevent loading the broken
persisted cache.

>   * ... but once again received that org-element-cache warning
>   * Now, after a fresh pull of code and a rebuild, NONE of the errors or
> warnings occur.

>
> Everything is clean now.
>
> Could loading those smaller files have cleaned or updated the cache?  Or 
> was it your code updates?

Every time you get parser error, the cache should be cleared. So, you
likely did clear the cache somewhere in the process.

In any case,
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=eb796ae4326faf246b1b1a382a0a6a372f28c9e4
should fix most of the "unregistered buffer modifications" warnings.
It will only show up in really serious cases.

Best,
Ihor

Re: [External] : Re: how to investigate? org-element-cache Unregistered buffer modifications detected

[Daniel Ortmann]

Hello,

... I rebuild at least once per day.
My current org-mode version is:
Org mode version 9.5.4 (release_9.5.4-596-gaa5bc2 @ 
/home/dortmann/src/git-org-mode/lisp/)


A bit more information may help?

 * 1.2MB org-mode file
 * received a stubborn parse error after today's build; could not load
   my org file; the file location looked fine
 * partitioned the large file into smaller files
 * ... was able to load each of those smaller files
 * afterwards, without any changes, I was able to load the full file
   without the 'parse error'
 * ... but once again received that org-element-cache warning
 * Now, after a fresh pull of code and a rebuild, NONE of the errors or
   warnings occur.


Everything is clean now.

Could loading those smaller files have cleaned or updated the cache?  Or 
was it your code updates?


Thank you!

On 6/28/22 21:03, Ihor Radchenko wrote:

Daniel Ortmann  writes:


Hey there,
I have a 1.2+ MB org-mode file and have been getting the following
message for a week or two.  I have cleaned up content by archiving older
content and have run org-lint to cleanup some syntax issues ...

How to debug this type of issue?

Thanks for reporting!
Could you please update you Org to the latest version and check if the
warning keep appearing? I just pushed a commit that changes the logic
when to show this type of warning (the previous logic had
false-positives too often).

Best,
Ihor

Re: Getting rid of org-install.el

[Stefan Kangas]

Ihor Radchenko  writes:

> > 2. Delete the file from org-mode.git
> > ...
> > What do you think?
>
> Sounds good to me.

Patch attached.
From d609398f5a42a0157c309ead3e38be8ea78456f8 Mon Sep 17 00:00:00 2001
From: Stefan Kangas 
Date: Wed, 29 Jun 2022 05:36:47 +0200
Subject: [PATCH] * lisp/org-install.el: Delete file.

See: 
---
 lisp/org-install.el | 17 -
 1 file changed, 17 deletions(-)
 delete mode 100644 lisp/org-install.el

diff --git a/lisp/org-install.el b/lisp/org-install.el
deleted file mode 100644
index d521d819d..0
--- a/lisp/org-install.el
+++ /dev/null
@@ -1,17 +0,0 @@
-;;; org-install.el --- backward compatibility file for obsolete configuration  -*- lexical-binding: t -*-
-;;
-;;; Code:
-;;
-;; The file org-install is obsolete.
-;;
-;; It is provided here so that (require 'org-install) does not
-;; trigger an error for users with obsolete Emacs configuration.
-;; You can safely remove (require 'org-install) from your config."
-
-(provide 'org-install)
-
-;; Local Variables:
-;; no-byte-compile: t
-;; coding: utf-8
-;; End:
-;;; org-install.el ends here
-- 
2.30.2

Re: Getting rid of org-install.el

[Kyle Meyer]

Stefan Kangas writes:

> org-install.el has been obsolete for more than 10 years.
>
> To finally get rid of this file, I put it to you that all we need to do is:
>
> 1. Move it in emacs.git from lisp/org/org-install.el to
> lisp/obsolete/org-install.el
> 2. Delete the file from org-mode.git

In my view it'd be better to drop the first item.  Org has removed
plenty of obsolete features in its time, but searching the emacs.git
history, I can't find a case where an Org-related file has been in
lisp/obsolete/.  I'd vote against setting that precedent, as I don't
want to introduce any more discrepancies between the Org files in
org-mode.git and emacs.git than necessary.

Re: [PATCH] Fix caption format for custom latex src block

[Ihor Radchenko]

Matt Huszagh  writes:

> Ihor Radchenko  writes:
>
>> I think that it will be better if you use
>> org-latex--caption/label-string instead. It will take care about short
>> captions as well.
>
> Changing this to (?c . ,caption-str) yields for the original example
>
> \caption{\caption{Perform inter-sample interpolation.}
> }
>
> I could use substring to remove the leading \caption{ and trailing
> }. What do you think?

Removing caption does not sound reliable. Also, you need to
update the patch according to recent commit by Timothy.

Timothy, looking at the new implementation of org-latex-src-block, I do
not see custom-env being passed as an argument of
org-latex-src-block--custom. This is likely a bug.

Best,
Ihor

Re: Getting rid of org-install.el

[Ihor Radchenko]

Stefan Kangas  writes:

> org-install.el has been obsolete for more than 10 years.
> ...
> 2. Delete the file from org-mode.git
> ...
> What do you think?

Sounds good to me.

Best,
Ihor

Re: [BUG] random org-mode warning [9.5.4 (9.5.4-g7c61a3 @ /home/cro/.emacs.default/straight/build/org/)]

[Ihor Radchenko]

Cristi Constantin  writes:

> Than you for the response! I tried the fix you suggested, but I still 
> see this:

I just pushed a commit that should hopefully fix this problem. Please
update Org and let me know if you keep seeing the warning.

Best,
Ihor

Re: how to investigate? org-element-cache Unregistered buffer modifications detected

[Ihor Radchenko]

Daniel Ortmann  writes:

> Hey there,
> I have a 1.2+ MB org-mode file and have been getting the following 
> message for a week or two.  I have cleaned up content by archiving older 
> content and have run org-lint to cleanup some syntax issues ...
>
> How to debug this type of issue?

Thanks for reporting!
Could you please update you Org to the latest version and check if the
warning keep appearing? I just pushed a commit that changes the logic
when to show this type of warning (the previous logic had
false-positives too often).

Best,
Ihor

Re: Dates in headlines

[Samuel Wales]

this iirc has been obsolete for many years and ime and on ml never was
an issue.  i tried to find out why it was mentioned but did not find
anything.  it might have been an ambiguity in the manual to do with
active tses like in your example?  e.g. the agenda will remove the
active ts at least in certain cases, but that is a deliberate feature.

i successfully rely on inactive as below.  they are sorted by the ts.
a capture template inserts them.

much better than date trees for my case.  always show, sorted at
bottom, no hierarchy, nothing out of sync, can scan and bisect to find
an entry or get a sense of number, can change a ts and sort again,
looks the same in the agenda, etc.


* LOG [2021-07-01 Thu] vulcans mediating with klingons
* LOG [2021-06-28 Mon 15:44] brawl.  scottie of course :(.
* LOG [2021-06-28 Mon 15:44] hauled away AS garbage?
* LOG [2021-06-28 Mon 15:44] klingons said garbage scow


On 6/28/22, Ypo  wrote:
> I think I've read somewhere that it is a "bad practice" to use dates in
> headlines, is it correct? I haven't found it in the manual.
>
> Like:
>
>  <2022-06-29 mi. 10:30> Meeting
>
> Best regards
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com

how to investigate? org-element-cache Unregistered buffer modifications detected

[Daniel Ortmann]

Hey there,
I have a 1.2+ MB org-mode file and have been getting the following 
message for a week or two.  I have cleaned up content by archiving older 
content and have run org-lint to cleanup some syntax issues ...


How to debug this type of issue?

Warning (org-element-cache): org-element--cache: Unregistered buffer 
modifications detected. Resetting.
If this warning appears regularly, please report the warning text to Org 
mode mailing list (M-x org-submit-bug-report).

The buffer is: plan.org
 Current command: (org-agenda 4070 5168)
 Chars modified: 4070
 Buffer modified: 5168
 Backtrace:
nil Disable showing Disable logging

Thank you for your guidance.

Re: Dates in headlines

[Jean Louis]

On 2022-06-28 12:06, Ypo wrote:

I think I've read somewhere that it is a "bad practice" to use dates
in headlines, is it correct? I haven't found it in the manual.

Like:

 <2022-06-29 mi. 10:30> Meeting

Best regards


In many of my notes I use dates in titles of the section. Note creation 
is not always equal to date to which not relates. When it is useful, use 
it.


--
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

Re: Links to javascript-based websites from orgmode.org: Paypal and Github

[Michael Powe]

On 6/27/2022 21:54, Ihor Radchenko wrote:

Michael Powe  writes:


Anyone completely serious about a refusal to use nonfree tools for
making donations will send a check in the mail, literally.

Would providing something like
"Contact us via email if you prefer to make a donation using alternative
mechanism"
help if we add such statement to https://liberapay.com/org-mode page?


Hello,

I think it would be good to let people know that they could do so.

In re: the mailing address, this should be a post office box, or 
possibly, a business address, not a residential street address. Aside 
from the privacy concern of putting your personal address out there, I 
think it's better marketing to avoid telling users to send their money 
to someone's home. ;-)


Now, I've been using the business name "MAP Analytics" above my home 
address for years. The business exists only in my imagination, but it 
serves the purpose when an "organization" name is required.


Thanks.

mp

--
"Do not neglect to do good, and to share what you have." - Hebrews 13:16a
Michael Powe
Naugatuck CT USA
po...@ctpowe.net

Re: org-babal-R-command

[Naresh Gurbuxani]

It works!  You made my day.

Thanks,
Naresh

Sent from my iPhone

> On Jun 28, 2022, at 2:40 PM, Bruno Barbier  wrote:
> 
> Naresh Gurbuxani  writes:
> 
>> In my windows computer, R is installed at c:/Program Files/Microsoft/R 
>> Open/R-3.5.1/bin
>> 
>> Notice two spaces: “Program Files” and “R Open”
>> 
>> How can I set the variable org-babel-R-command?
>> 
>> I tried
>> (setq org-babel-R-command “c:/Progra~1/Microsoft/R Open/R-3.5.1/bin/R.exe 
>> —slave —no-save”)
>> 
>> But the space between R and Open is a problem.  What is the solution?
> 
> Maybe this will work (quoting the path between "):
> 
>  (setq org-babel-R-command “\"c:/Progra~1/Microsoft/R 
> Open/R-3.5.1/bin/R.exe\" —slave —no-save”)
> 
> 
> 
>> 
>> Thanks,
>> Naresh
>> 
>> Sent from my iPhone

Re: org-babal-R-command

[Bruno Barbier]

Naresh Gurbuxani  writes:

> In my windows computer, R is installed at c:/Program Files/Microsoft/R 
> Open/R-3.5.1/bin
>
> Notice two spaces: “Program Files” and “R Open”
>
> How can I set the variable org-babel-R-command?
>
> I tried
> (setq org-babel-R-command “c:/Progra~1/Microsoft/R Open/R-3.5.1/bin/R.exe 
> —slave —no-save”)
>
> But the space between R and Open is a problem.  What is the solution?

Maybe this will work (quoting the path between "):

  (setq org-babel-R-command “\"c:/Progra~1/Microsoft/R Open/R-3.5.1/bin/R.exe\" 
—slave —no-save”)


  
>
> Thanks,
> Naresh
>
> Sent from my iPhone

Re: Eshell automatically inserting spurious tabs

[Alessandro Bertulli]

Ihor Radchenko  writes:

> Note that you are writing to the mailing list dedicate to Org mode. Your
> issue does not appear relevant. You may have better luck asking
> emacs-help mailing list, #emacs IRC, or /r/emacs reddit.

My bad! I meant to write to Emacs mailing list but apparently I
triggered the wrong completion in my .mailrc .
I didn't check, sorry!

I'll forward my request to the correct list.

Alessandro

Getting rid of org-install.el

[Stefan Kangas]

org-install.el has been obsolete for more than 10 years.

To finally get rid of this file, I put it to you that all we need to do is:

1. Move it in emacs.git from lisp/org/org-install.el to
lisp/obsolete/org-install.el
2. Delete the file from org-mode.git

This means that all users (of old and new versions) will have a bundled
org-install.el so that requiring it still works, but on Emacs 29 or later
you will get the usual obsoletion warnings.  The file would finally be
removed from emacs.git in another decade or so according to current Emacs
maintenance practices.

What do you think?

Re: org-cite: only last names and et al. for more than two coauthors

[Bruce D'Arcus]

On Tue, Jun 28, 2022 at 10:10 AM M. Pger  wrote:

> A last question though: is it possible to set the 'round' option without 
> having to insert the latex header
> ```
> #+LATEX_HEADER: \usepackage[round]{natbib}
> ```
> ?

I haven't used it, but I believe the ~org-cite-natbib-options~
defcustom is what you need.

Bruce

Re: org-cite: only last names and et al. for more than two coauthors

[M. Pger]

Hi, thx for your answer.
Sorry for my poor understanding of org-cite. I added
```
(require 'oc-natbib)
(setq org-cite-export-processors
  '((latex natbib)
(t basic)))
```
to my init file and then it worked smoothly. I can even put
```
#+cite_export: natbib customstylefile.bst
```
in my org file to use an extraneous bibliography style file, which is pretty 
nice.

A last question though: is it possible to set the 'round' option without having 
to insert the latex header
```
#+LATEX_HEADER: \usepackage[round]{natbib}
```
?

Thanks a lot for your work with org-cite.

Best,

M

--- Original Message ---
On Monday, June 27th, 2022 at 12:56 PM, Bruce D'Arcus  wrote:


> On Mon, Jun 27, 2022 at 1:13 AM M. Pger mp...@protonmail.com wrote:
>
> > I've recently tried to switch to org-cite, but I still have some problems 
> > with the basics.
>
>
> First, org-cite is a framework for citations. When reporting issues
> related to it, you really need to identify what processor(s) you are
> seeing the behavior with.
>
> > Consider the following entry:
> >
> > @article{akey2022,
> > title = {This is the title},
> > shorttitle = {This is the short title},
> > author = {Surname1, Name1 and Surname2, Name2 and Surname3, Name3},
> > year = {2022},
> > (truncated)
> > }
> >
> > I want to have something like: "as shown by Surname1 et al. (2022), ...", 
> > i.e. something one can get with natbib \citet command. With org-ref it 
> > worked like a charm.
> >
> > I've tried the syntax presented in 
> > https://blog.tecosaur.com/tmio/2021-07-31-citations.html#more-exporting, 
> > that is:
> > [cite/t/c:@akey2022]
> > but I ended with a 'wrong type argument' error.
> >
> > I then tried [cite/t:@akey2022]: exporting succeeds. However, I end up with 
> > "as shown by Surname1, Name1 and Surname2, Name2 and Surname3, Name3 
> > (2022), ...".
> >
> > How can I correctly specify the options mentioned above? Is there a 
> > complete and updated tutorial available somewhere?
>
>
> [cite/t:@key] should work as you expect in natbib, biblatex, csl.
>
> Possible issues, depending on which of those you're using:
>
> - some error with the bib file; or a mismatch between the file and the
> bibtex dialect or something
> - the citation style
>
> A complete MWE would help.
>
> Bruce

org-babal-R-command

[Naresh Gurbuxani]

In my windows computer, R is installed at c:/Program Files/Microsoft/R 
Open/R-3.5.1/bin

Notice two spaces: “Program Files” and “R Open”

How can I set the variable org-babel-R-command?

I tried
(setq org-babel-R-command “c:/Progra~1/Microsoft/R Open/R-3.5.1/bin/R.exe 
—slave —no-save”)

But the space between R and Open is a problem.  What is the solution?

Thanks,
Naresh

Sent from my iPhone

Re: [PATCH] describe how to override Author

[Robert Pluim]

> On Mon, 27 Jun 2022 17:53:30 +0800, Ihor Radchenko  
> said:

Ihor> Robert Pluim  writes:
>> diff --git a/org-contribute.org b/org-contribute.org

Ihor> Maybe add the details to org-maintenance.org instead?
Ihor> This is more of a technical detail needed for maintainers, not for the
Ihor> committers.

Iʼd be worried if the org maintainer(s) didnʼt know how to override
Author :-)

Occasional committers would probably not read org-maintenance.org, and
those are the people this section is aimed at, I think. Plus itʼs the
kind of thing you need to catch early: once the commit has been pushed
itʼs too late.

>> +1. Command line: src_sh{git commit --author='First Last 
'}

Ihor> I think we usually prefer source blocks to inline source blocks.

OK, changed.

>> +2. =VC=: Set the 'Author:' field in log-edit mode (requires setting
>> +   `log-edit-setup-add-author').

Ihor> 'Author:' -> =Author:=
Ihor> `log-edit-setup-add-author' -> ~log-edit-setup-add-author~ 

OK, changed.

Robert
-- 

Dates in headlines

[Ypo]

I think I've read somewhere that it is a "bad practice" to use dates in 
headlines, is it correct? I haven't found it in the manual.


Like:

 <2022-06-29 mi. 10:30> Meeting

Best regards

Re: Org, Hyperbole, and eev

[Robert Weiner]

Hi Eduardo:

Many programmers refuse to document almost anything and expect the code to
speak for itself.  Or they throw random comments throughout their code that
don't help elucidate things.  The nice thing about most Elisp code is that
the inputs and outputs of functions are often pretty well documented, since
people learn from many good examples.  I support you in wanting to document
and explain things very clearly for your readers.  For most people,
Hyperbole is extensively documented down to the function-level.  But you
want an 'atomic'-level description of the internals of Hyperbole which I
think would be useful to only a very small population.

Good programming is about producing and layering clean abstractions that
sometimes must mask internal complexity and expose only the interfaces
necessary for use (could be a UI, an API or a class abstraction).  It's not
turtles all the way down as the 'physics' of different levels of
implementation varies.  Hackers do build from lego blocks; they don't spend
their time trying to deconstruct everything just to get comfortable with
every component they use, in general.  If you want to spend years trying to
wrap your mind around something a bit complex then read The Art of the
Meta-object Protocol many times.  Then, if you survive, come back to
Hyperbole and its call tree will seem simple to you :-)

Seriously though, I get that you learn and document differently than many
other people, so just do your own thing, your own way.  I am reminded of
the Hudsucker Proxy where the 'rube' is derided for his stupid idea until
later it turns out to be one of the most profitable inventions in history.
Maybe the rest of us just can't see what you see because of the way you
express it, though if we could, we would be enthralled.  I know a bit what
that is like!

Best of luck,

-- rsw

On Tue, Jun 28, 2022 at 12:48 AM Eduardo Ochs  wrote:

> On Sun, 26 Jun 2022 at 21:50, Robert Weiner  wrote:
> >
> > So here is a simple implementation that is not unlike your own
> > though the functions are a bit simpler and more clearly documented
> > _without a listing of every possible test case type_ and requires
> > neither Hyperbole nor Org until you want to activate things as
> > buttons:
>
>
> Hi Robert,
>
> I think that the part in "_..._"s above deserves a detailed answer.
>
> I started using GNU/Linux in the mid-90s. Before that my favorite
> languages were Icon and Forth. In Forth I could do AMAZING things in
> less than 50 lines of code, but my programs would usually become
> confusing and unmanageable when they grew bigger than that.
>
> There is a famous book by Fred Brooks called "The Mythical Man-Month",
> and one of its chapters is called "Plan to Throw One Away":
>
>   https://wiki.c2.com/?PlanToThrowOneAway
>
> I took that slogan seriously. Most of the time when I realized that
> something that I was doing by hand could be automated I would write a
> first attempt to automate it - _as a prototype_, that I regarded
> partly a program and partly as a way to help me think how that task
> could be structured, and that would probably be "thrown away" if I
> needed a cleaner solution later.
>
> In Forth it was very easy to implement both strange interfaces and
> little languages, in this sense:
>
>   https://wiki.c2.com/?LittleLanguage
>
> In Emacs less so, but I could still do lots of funny things using
> eval-last-sexp to use sexps as buttons.
>
> When we are writing throwaway code "planning to throw one away" then
> using tests in comments is a very good way to document the code. And
> when I rewrite my prototypes I usually prefer to document them using
> text ***AND*** executable examples rather than just text. One of the
> effects of using this style is that the users of eev see that they can
> use that style in their notes too - and with that their notes become
> much closer to being "executable notes", in this sense,
>
>   http://angg.twu.net/eev-intros/find-here-links-intro.html
>
> than they would be if they believed that they had to write the docs of
> their functions as just text.
>
> You are sort of saying that having tests in comments is bad style.
> Well, it's not. =/
>
>   [[]],
> Eduardo Ochs
> http://angg.twu.net/#eev
>

Re: Links to javascript-based websites from orgmode.org: Paypal and Github

[Tim Cross]

"Dr. Arne Babenhauserheide"  writes:

> [[PGP Signed Part:Undecided]]
>
> Richard Stallman  writes:
>
>> [[[ To any NSA and FBI agents reading my email: please consider]]]
>> [[[ whether defending the US Constitution against all enemies, ]]]
>> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>>
>>   > AFAIU, there are no nonfree payment services, except some crypto
>>   > payments.
>>
>> In Europe, at least, there is bank transfer.  If you go to a bank
>> branch, I think, you can do transfers to someone else's account without
>> running any particular software.
>
> This is becoming harder and harder, because banks push everyone to use
> onlinebanking — with non-free apps and non-free Javascript. And it costs
> money: A bank transfer by going to the branch is nowadays more expensive
> than the amount people usually donate per month.
>

Yes, in Australia, there are many rural towns which no longer have any
local bank branch at all. You might have to travel 100s of miles to
reach a bank branch office (and there won't be any public transport
either). The push is very much towards on-line services and I very much
doubt there is a single bank in Australia which doesn't use non-free
Javascript in their interface.

Still, my main point, which I note RMS did not comment on, is that if
the FSF can have a link to Paypal (with a note stating it is not
recommended), then I don't see why a GNU project cannot do similar. All
that is necessary is to provide an alternative, which could be as simple
as a postal address to send donations to. Concerns over privacy of the
address can be dealt with by using a post box or a mail service, though
I don't see any major issue to be concerned about wrt a mail address.

Re: Links to javascript-based websites from orgmode.org: Paypal and Github

[Dr. Arne Babenhauserheide]

Richard Stallman  writes:

> [[[ To any NSA and FBI agents reading my email: please consider]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > AFAIU, there are no nonfree payment services, except some crypto
>   > payments.
>
> In Europe, at least, there is bank transfer.  If you go to a bank
> branch, I think, you can do transfers to someone else's account without
> running any particular software.

This is becoming harder and harder, because banks push everyone to use
onlinebanking — with non-free apps and non-free Javascript. And it costs
money: A bank transfer by going to the branch is nowadays more expensive
than the amount people usually donate per month.

>   > So, does what you say imply that GNU packages should not provide any
>   > donation options, except crypto (via free payment software)?
>
> Yes, sad to say they should not directly offer donation methods.

So they should rather link to liberapay, so it is not a direct offer?

After the initial setup liberapay usually does the automatic renewal, so
it is not necessary to interact with non-free Javascript after the
initial setup. That’s not perfect, but much better than PayPal.
https://liberapay.com/about/payment-processors

> The FSF manages to accept credit card donations without making donors
> run nonfree software.  But it is not easy to arrange that.

And it does not work for many people in Europe (I for example have no
credit card).

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de


signature.asc
Description: PGP signature

Re: feature proposal: export to html headless

[Uwe Brauer]

>>> "MN" == Max Nikulin  writes:

> On 27/06/2022 19:11, Uwe Brauer wrote:
>>> [it isn't an answer for you because you want it in the menu.  others
>>> will field that.  and it's similar to your code.]
>> Right, I hope somebody does, because it looks rather complicated
>> when I look for it in ox.el

> Isn't the following entry of the export menu is what you are asking
> for? I am unsure however if "headless" in your request is the same as
> "body-only" in the Org code.

> [C-b] Body only:Off   [C-v] Visible only: Off
> ^^^
> [C-s] Export scope: Buffer[C-f] Force publishing: Off
> [C-a] Async export: Off

Ok by god, I did not notice that. I will test it. Thanks very much



-- 
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine. 


smime.p7s
Description: S/MIME cryptographic signature

Re: Org, Hyperbole, and eev

[Eduardo Ochs]

On Mon, 27 Jun 2022 at 01:11, Robert Weiner  wrote:
>
> These are Action buttons run by the action button type defined via
> the defib macro in the “hibtypes.el” file.  Just search for ‘defib
> action’ in there.  You can invoke its implicit button type function
> from Lisp as (ibtypes::action) if I recall.


Hi Robert and other people,

I was finally able to understand a significant part of what happens
when we type M-RET on an action button like

  

with hyperbole-mode active... my notes are here - for the sake of
completeness; I don't expect them to be readable -

  (code-c-d "hyperbole" "~/.emacs.d/elpa/hyperbole-8.0.0/")
  (require 'hyperbole)
  (hyperbole-mode 0)
  (find-hyperbolefile "DEMO")
  (find-hyperbolefile "DEMO" "Action Key is {M-RET}")
  (find-hyperbolegrep "grep -nH --null -e M-RET *")
  (find-efunction 'hkey-initialize)
  (find-efunction 'hkey-initialize "Bind the Action Key to {M-RET}")
  (find-ekeymapdescr hyperbole-mode-map)
  (find-ekeymapdescr hyperbole-mode-map "M-RET")
  (find-ekeymapdescr hyperbole-mode-map "M-RET" "hkey-either")
  (find-efunction 'hkey-either)
   (find-efunction 'assist-key)
   (find-efunction 'assist-key-internal)
  (find-efunction 'action-key)
  (find-efunction 'action-key-internal)
  (find-efunction 'hkey-execute)
  (find-efunction 'hkey-execute "hkey-alist")
  (find-evardescr 'hkey-alist)
  (find-eppp   hkey-alist)
  (find-eppp   hkey-alist "(hbut:at-p)")
  (find-evariable 'hkey-alist)
  (find-evariable 'hkey-alist "If on a Hyperbole button")
  (find-evariable 'hkey-alist "If on a Hyperbole button" "(hbut:at-p)")
  (find-efunction 'hbut:at-p)
  (find-efunction 'hbut:at-p "ebut:at-p")
  (find-efunction 'hbut:at-p "ibut:at-p")
   (find-efunction 'ebut:at-p)
   (find-efunction 'ebut:get)
  (find-efunction 'ibut:at-p)

  https://lists.gnu.org/archive/html/emacs-orgmode/2022-06/msg00765.html
^ mentions ibtypes::action and defib action

  (find-efunction 'defib)
  (find-hyperbolegrep "grep --color=auto -nH --null -e defib *.el")
  (find-hyperbolegrep "grep   -a -nH --null -e defib hibtypes.el")
  (find-hyperbolefile "hibtypes.el" "(defib action")

  (progn
(find-hyperbolefile "hibtypes.el" "(defib action")
(end-of-defun)
(setq ee-defib-defun (ee-last-sexp))
)

  (find-estringee-defib-defun)
  (find-epp  (read ee-defib-defun))
  (find-eppm (read ee-defib-defun))
  (find-efunction 'htype:create)
  (find-efunction 'htype:symbol)
  (htype:symbol 'action 'ibtypes)
  (find-efunction   'ibtypes::action)
  (find-efunctionpp 'ibtypes::action)

  (load "hibtypes.elc")
  (load "hibtypes.el")

  (find-efunctionpp 'ibtypes::action)

  (hyperbole-mode 1)
  (debug-on-entry 'ibtypes::action)

(eek "2* C-e ")
(eek   " C-e  M-RET")


  (hyperbole-mode 0)

  (find-efunction 'ibut:at-p)
  (find-efunction 'ibut:at-p "(funcall itype)")
  (find-eppp (htype:category 'ibtypes))

  (find-hyperbolegrep "grep -a -nH --null -e defib hibtypes.el")
  (find-efunction 'symtable:add)
  (find-evardescr 'symtable:ibtypes)
  (find-evariable 'symtable:ibtypes)

I still don't understand well the code of ibut:at-p between the
beginning and the point in which it calls (funcall itype), and I also
don't understand well the code of ibtypes::action...

Anyway, we are clearly using different notions of simplicity - see:

  https://lists.gnu.org/archive/html/hyperbole-users/2020-09/msg00013.html

and I find it enviable that you can have that kind of complexity under
the hood and still have lots of users that agree that Hyperbole is
"simple"...

Most people find eev very weird, and I have the impression that I
wouldn't have half of my (few) users if I had code like that in eev.
If the people who like to look under the hood try to understand how
M-e in eev works they will end up trying to understand how

  (forward-sexp -1)

works, and then they will read the comments of scan-sexps in
syntax.c... syntax.c is impeccably well-written, and they will
probably feel that their time was very well spent, and that their
curiosity has lead them to very good places. =\

  Exhausted cheers,
Eduardo Ochs
http://angg.twu.net/#eev