Re: org-no-popups nilling display-buffer-alist

[Kyle Meyer]

\"Joshua O'Connor\" writes:

> Hi,
> I wanted to control the positioning of the *Org Select* buffer, so I
> first went to add a rule to 'display-buffer-alist'.
> But I found it didn't work, as the function in question calls
> 'org-switch-to-buffer-other-window', which in turn calls an odd macro
> 'org-no-popups', which appears to let-nil the 'display-buffer-alist'.
>
> I was wondering what the reason is for this? To me I expected this
> variable to be reserved for me as a user to choose where windows can go,
> which I think is a good plan given that you cannot possible know all the
> configurations a user may want the window to appear.

I agree that this should left to the user, and in 9.4 there was at least
some progress in making Org behave better in this department:
.

I've yet to do any extensive digging, but I suspect there wasn't a
strong reason for doing this.  I'd be in favor of a patch that drops the
use of display-buffer-alist.

Recalculate mixed tables/source blocks

[Ethan Glasser-Camp]

Hi! I've been learning about the spreadsheet features of org-table and how
to use them with org-babel. They're both really cool and I was happy to be
able to convert a Gnumeric spreadsheet into something that I can keep in
version control.

Now I have a document that consists of mutually-referential tables and
source blocks. So, for example, I have table A, then table B which refers
to table A, then source block C which accesses table B using a noweb
reference, and finally table D which uses the output of source block C in
its formulas.

I want to be able to change the "inputs" in table A and see the updates in
table D. So far the easiest way I have found to do this is to use
`org-table-recalculate-buffer-tables`, then `org-babel-execute-buffer`,
then `org-table-recalculate-buffer-tables` again. I already made at least
one mistake by rerunning the source block without remembering to refresh
intermediate tables. I was wondering if there is another way, either
simpler or more robust?

Thanks!

Ethan

[Please cc me on replies, I'm not subscribed to the list.]

Re: Auto-activate new <<>>

[Kyle Meyer]

Adam Sneller writes:

> I want to call org-update-radio-target-regexp as soon as org-mode
> recognises a new <<>> has been created (which seems to
> happen as soon as the third ">" is typed).
>
> What hook can I use to get this done?

I'm not spotting any hook that could be used for this.  The <<>>
fontification happens through a simple 'regular expression => face'
mapping in org-font-lock-keywords.

You're probably aware of this and it's just not as automatic as you'd
like, but just in case: pressing `C-c C-c' with point on <<>
will call org-update-radio-target-regexp.

Re: [PATCH] document org-html-meta-tags

[Kyle Meyer]

TEC writes:

> Hi Kyle, All,
>
> As requested, here's a small documentation entry for the new setting :)

Thanks.  Pushed (5b0eb9aad) with the tweaks mentioned below.

> diff --git a/doc/org-manual.org b/doc/org-manual.org
> index 20a0d1d7a..a82b0f9a4 100644
> --- a/doc/org-manual.org
> +++ b/doc/org-manual.org
> @@ -12624,6 +12624,9 @@ settings described in [[*Export Settings]].
>multiple =DESCRIPTION= lines.  The exporter takes care of wrapping
>the lines properly.
>  
> +  The exporter includes a number of other meta tags, which can be customised
> +  by modifying ~org-html-meta-tags~.
> +

s/customised/customized/ to follow Emacs's preference for American
English in documentation.

Of course it doesn't really matter, but if it's left as is, it will
likely lead to unnecessary work on for some Emacs developer.  (The Emacs
repo has commits of tree-wide cleanups making this exact substitution.)

>  - =HTML_DOCTYPE= ::
>  
>#+cindex: @samp{HTML_DOCTYPE}, keyword
> diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
> index ba769224f..a2f1667b2 100644
> --- a/etc/ORG-NEWS
> +++ b/etc/ORG-NEWS
> @@ -81,6 +81,13 @@ block. ~org-babel-latex-preamble~, 
> ~org-babel-latex-begin-env~ and
>  the user to specify the preamble and code that preceedes and proceeds
>  the contents of the source block.
>  
> +*** New option ~org-html-meta-tags~  allows for HTML meta tags customisation
> +
> +New variable ~org-html-meta-tags~ makes it possible to customise the
> +== tags used in an HTML export. Accepts either a static list of

In addition to more s/customis/customiz/, I dropped the extra space
before "allows"...  and added another space before "Accepts".

> Oh, by the way --- [...]

Sorry, I don't have the bandwidth at the moment for that discussion.

Auto-activate new <<>>

[Adam Sneller]

I want to call org-update-radio-target-regexp as soon as org-mode recognises a 
new <<>> has been created (which seems to happen as soon as the 
third ">" is typed).

What hook can I use to get this done?

Adam Sneller – CCO
MS2 Digital
20 Old Bailey, St Paul's, ​London EC4M 7AN
​adam.sneller@ms2.digital
office: 020 3988 6800
direct: 020 3988 6809
The information in this e-mail and any documents and files transmitted with it 
are confidential and for the use of the intended recipient only. If you are not 
the intended recipient, please delete the message and any attachments 
immediately and notify the sender. Although MS2 Group Limited believes this 
e-mail and any attachments are free of any virus or other defect which may 
affect a computer, it is the responsibility of the recipient to ensure that it 
is virus free and MS2 Group Limited does not accept any responsibility for any 
loss or damage arising from its use. MS2 Group Limited is registered in England 
and Wales, company number 10410414. Registered office: 27 Old Gloucester 
Street, London WC1N 3AX. 'MS2 Digital' is the trading name of MS2 Group Limited.
​
​© 2020 MS2 Group Limited