Re: Interest in an Org video meetup?

2022-11-07 Thread Ihor Radchenko
Russell Adams  writes:

> One of my concerns is the format. I used to goto user groups
> frequently, and we could break up into smaller groups working on many
> things.
>
> On the other hand, tools like BBB or Jitsi tend to be best for a
> presenter and an audience.
>
> I'm ok with prepping a presentation and a sample org file or two, and
> answering questions in a group setting.

I am not sure if we even need to worry about multiple rooms. AFAIK,
Emacs meetups generally do not gather more than a dozen of people max.

I suggest you to try running an actual meetup first and see how many
people show up. It is not like you plan a single event and need to
account for all the possible scenarios. If there are too many people, we
can adjust the format in the later meetings.

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



Re: [PATCH] rfc: using ert-deftest with side-effects

2022-11-07 Thread Ihor Radchenko
Leo Butler  writes:

> However, I would like feedback/suggestions on writing such a
> test. Issues include:
>
> 1. how to clean up the side-effects, including changes in the test
>buffer, filesystem and potentially creating an error buffer;

As you did, we generally use unwind-protect. Also, we prefer putting
temporary files into temporary directory.

You can grep for `make-temp-file' and `delete-file' in tests. There are
plenty of examples.

> 2. the general absence of similar tests (except in test-ob.el,
>test-ob/result-graphics-link-type-header-argument).
> ...
> I am unsure about 2. Is the absence of such tests because there is a
> policy against them, or ...

We have no such policy. In fact, many tests are making
temporary files.

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



Typos on https://orgmode.org/manuals.html

2022-11-07 Thread Loris Bennett
Hi,

Under the heading 

  Org Mode compact guide

it says

  The Org Mode compact guide is a shorter introduction to the main
  feature of Org Mode.

This should probably be

  ... features of Org Mode.

Under the heading

  Org manual for the GNU Emacs version

it says

  GNU Emacs publishes manual for core features, included Org. 

I'm not exactly sure what is meant here, possibly something like

  The GNU Emacs manual also includes the Org manual. 

Cheers,

Loris

-- 
This signature is currently under construction.



Re: [PATCH] oc-csl: Improve LaTeX bibliography formatting

2022-11-07 Thread Ihor Radchenko
András Simonyi  writes:

>> Also, it would be nice to describe CSL usage and tweaks in the manual.
>
> Time permitting I may try to add something, but wouldn't it be a
> problem if the CSL export processor was discussed in much more detail
> than the others?
> I was also thinking about providing a list of available citation
> substyles but I do not want to make the manual very unbalanced.

Maybe not in the release, but otherwise we need to finish the citation
section of the manual one way or another. May as well start from CSL
part.

>> I have two comments here:
>> 1. Where are all these new commands coming from? They are not used
>>directly in the code. Are you tweaking citeproc.el output this way? May
>>it be better to use customizations provided by citeproc.el itself?
>
> Yes, the citeproc org-latex formatter, which I added specifically for
> Org, uses these commands in the LaTeX code produced for the
> bibliography. As citeproc doesn't have customizable variables by
> design (if I recall correctly, the only exception is 2 hooks), and
> oc-csl already had some variables concerned with very similar
> formatting settings (org-cite-csl-latex-hanging-indent,
> org-cite-csl-html-hanging-indent,
> org-cite-csl-html-label-width-per-char) I think it is more consistent
> to have the new ones also in Org.

Thanks for the clarification. I'd prefer to see a similar explanation
and the details about what the LaTeX variables/commands do in the
docstring.

>> 2. You are declaring this variable as defcustom, but it is not clear
>>what is going to happen if the user changes it. It is not how to
>>change this template in meaningful ways either.
>
> Right, I can try to detail a bit in the docstring what type of
> commands and environments have to be provided by the preamble (are
> expected by citeproc). I tried to follow Timothy's handling of the
> ox-latex engraved preamble, but a simpler alternative would be to
> treat it simply as a constant template, at least for the time being --
> WDYT?

Note that `org-latex-engraved-preamble' explains which packages need to
be loaded and which commands need to be defined in the preamble. This at
least make it more clear what the users may change and not break the
export.

I see not problem keeping this a defcustom, but we definitely need to
explain the default value and what is required to be in there. At least,
to make the code readable for future contributors.

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



Re: [PATCH] Re: Update Org to MathJax 3

2022-11-07 Thread Ihor Radchenko
Rudolf Adamkovič  writes:

> Ihor Radchenko  writes:
>
>> The proper test is not presence of the message, but the correct
>> conversion of the legacy options in the actual html output.
>
> We do test the results in the HTML output, of course.  Still, I would
> like to test the user messages too.

Then, you can `cl-letf'-bind the message function in a new macro added
to org-test.el. The binding will accumulate messages in some list. Then,
use that macro to test the messages.

Also, I think that conversion message may worth a warning.

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



Re: [PATCH] org-attach.el: ID to path functions may return nil

2022-11-07 Thread Ihor Radchenko
Max Nikulin  writes:

>> AFAIU, your version of `org-attach-dir-from-id' may sometimes return
>> nil, which is neither documented
>
> "otherwise independently of TRY-ALL
> value return the first non nil value."
>
> indirectly assumes nil. It may be made more prominent.

I feel like this makes the docstring confusing.

Note that `org-attach-id-to-path-function-list':

List of functions parsing an ID string into a folder-path.
The first function in this list defines the preferred function
which will be used when creating new attachment folders.  All
functions of this list will be tried when looking for existing
attachment folders based on ID.

The docstring implies that only the first function will be used to
create new attachment folders. With your patch, it will no longer be the
case and may surprise users.

You at least need to update the docstring.

> If TRY-ALL is non-nil, try all id-to-path functions in
> `org-attach-id-to-path-function-list' and return the first path
> that exist in the filesystem, otherwise independently of TRY-ALL
> value return the first non nil value.

This is a very long sentence and I cannot clearly parse which sub-clause
is referenced by "otherwise".

>> nor expected by the callers.
>
> I see 2 direct callers and I am not aware of any problem with them.
>
>> In particular, `org-attach-dir-get-create' will throw unhelpful "No
>> attachment directory is associated with the current node" error.
>
> * H short
> :PROPERTIES:
> :ID:   ec
> :END:
>
> if: No attachment directory is associated with the current node, adjust 
> ‘org-attach-id-to-path-function-list’
>
> I do not think this message is unhelpful.

With your patch, such message will be displayed even when
`org-attach-preferred-new-method' is set to something other than 'id.
And the message will be wrong then.

> +(defun org-attach-id-fallback-folder-format (id)
> +  "May be added last to `org-attach-id-path-function-list'.

This is not a proper first line in a function docstring. First line must
describe what the function does.

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



Re: Docstrings and literate programming (good practices?)

2022-11-07 Thread Samuel Wales
another option that might work for many users [at least would work for
myself buyt needs are modest here]  is unbreakable multi-directinal
links such that you can link from a docstring to the manual or from
the manual to the docstring.

by multidirectional i mean you can have the same link, which also acts
as an anchor, in multiple places.  clicking would take you to the
ohter  if it is bidirectional, or show you a list of places or cycle
if it is multidirectional.  id markers.


On 11/4/22, Samuel Wales  wrote:
> On 11/4/22, Ihor Radchenko  wrote:
>> 1. We need to convert from Elisp docstring format to Org markup
>
> not sure what is needed here as it is just a brainstorm.  but i have a
> manual i am loath to copy docstrings into when they are already in the
> code.  i could adumbrate a bit i the manual but i alreadyu do that
> initially in the docstrings.
>
> first line is a good schelling point for this. b ut you are right
> there is no standard i am awre of for anything more thn that.
>
>> 2. More importantly, User manual is something to be written as a
>>coherent text; not an agglomeration of docstring. (Yes, I am aware of
>>the fact that it is not always the case in practice; But we should
>>not encourage the current situation)
>
> agreed, it is for a oherent text.  the docstrings wuold be in a
> section like "Commands you might like to run in this mode".  Or so.
> and have key bidings.
>
> they are not the whole manual.
>
>>
>> --
>> Ihor Radchenko // yantar92,
>> Org mode contributor,
>> Learn more about Org mode at .
>> Support Org development at ,
>> or support my work at 
>>
>
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>


-- 
The Kafka Pandemic

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



Re: Document management system with Org?

2022-11-07 Thread Samuel Wales
hi max,

welcome to org.

org-roam has been suggested but i do not use it so i will not address
that and will leave it to others.

org is a good choice for this kind of thing, but it is not clear to me
how much of it needs to be built on top of existing to get what you
ask for.  emacs is good at doing that, however.  there are parts of
org that are basically made for it.

if you want to tag and then use agenda, that offers powerful features,
as does the category property.  one possible issue is remembering to
tag.  that is why i mostly don't use tags.  but there is regexp search
also.

the manual is good.  the agenda is sort of dired-like.  it sounds like
tags and catgegories might work for you.

if you read about hte org-id system, that might help you to make
unbreakable links should you need them.

attachments were made for storing files.  i don't use those because
they don't add much value for me; i just use plain links and i use
variables because file links in org run substitute-in-file-name  as
another possibility i haven't fully integrated, ** paths with glob
links might in priniciple help if files stay in the general area but
pathnames change.

but attachments might work for you.  they are actively used by many.
they more or less do what you are asking.

they are only for files, however.  if you ever need more than files, i
forsee a need for some kind of system for syncing with generic links
and external documnets and internal documents, something along hte
lines of spookfox perhaps.

but you seem to need only files.  so attachments or file links might
work for you with agenda and tags and categories.

the org forest is hierarchical, which an hlpe you put your data in the
same place.  if you need to break that system, links, tags, and
categories might help to keep your documents findable.  there are also
packges for transclusion.


On 11/7/22, Max Brieiev  wrote:
> Org newbie here.
>
> Org advertizes itself as a note management and organizer system.
>
> How suitable is it to manage documents?
>
> Documents are files, usually in pdf format, stored as blobs on file
> system. I need to attach some meta data to them. Like tags, for example,
> 'invoice' or 'contract' or some random notes.
>
> I would also like to have a way to categorize a group of documents by
> some criteria, e.g. by the name of a contractor.
>
> It would be good to have a dired-like interface to browse documents and
> manipulate them: view/copy/delete/attach to email etc.
>
> What approach could I use for this?
> Is there anything like that in Org ecosystem?
>
> Thanks.
>
>


-- 
The Kafka Pandemic

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



Re: [PATCH] Re: Update Org to MathJax 3

2022-11-07 Thread Rudolf Adamkovič
Ihor Radchenko  writes:

> The proper test is not presence of the message, but the correct
> conversion of the legacy options in the actual html output.

We do test the results in the HTML output, of course.  Still, I would
like to test the user messages too.  By my definition, "proper" tests
verify all requirements.  Hence, I ask: Do we want to reliably notify
the user?  If we do not, we can remove the messages.  If we do, then we
either test the messages or they will break at some random point in time
and generate yet another pointless mail thread.

If we do not have any better idea, then I can define a variable that
points to the 'message' function by default.  The relevant tests can
then set the variable to a function that gathers messages in a list.
With that, the tests can verify that the list contains exactly one
instance of the expected message.

Rudy
-- 
"It is no paradox to say that in our most theoretical moods we may be
nearest to our most practical applications."
-- Alfred North Whitehead, 1861-1947

Rudolf Adamkovič  [he/him]
Studenohorská 25
84103 Bratislava
Slovakia



Re: Document management system with Org?

2022-11-07 Thread Bill Burdick
I use orgroam for this sort of thing: https://www.orgroam.com/ In fact, I
manage most of my org files with orgroam.


-- Bill


On Mon, Nov 7, 2022 at 9:52 PM Max Brieiev  wrote:

> Org newbie here.
>
> Org advertizes itself as a note management and organizer system.
>
> How suitable is it to manage documents?
>
> Documents are files, usually in pdf format, stored as blobs on file
> system. I need to attach some meta data to them. Like tags, for example,
> 'invoice' or 'contract' or some random notes.
>
> I would also like to have a way to categorize a group of documents by
> some criteria, e.g. by the name of a contractor.
>
> It would be good to have a dired-like interface to browse documents and
> manipulate them: view/copy/delete/attach to email etc.
>
> What approach could I use for this?
> Is there anything like that in Org ecosystem?
>
> Thanks.
>
>


Document management system with Org?

2022-11-07 Thread Max Brieiev
Org newbie here.

Org advertizes itself as a note management and organizer system.

How suitable is it to manage documents?

Documents are files, usually in pdf format, stored as blobs on file
system. I need to attach some meta data to them. Like tags, for example,
'invoice' or 'contract' or some random notes.

I would also like to have a way to categorize a group of documents by
some criteria, e.g. by the name of a contractor.

It would be good to have a dired-like interface to browse documents and
manipulate them: view/copy/delete/attach to email etc.

What approach could I use for this?
Is there anything like that in Org ecosystem?

Thanks.



Re: @string abbreviation in bib file not honored in (basic) org-cite

2022-11-07 Thread Joost Kremers


On Sat, Nov 05 2022, Ihor Radchenko wrote:
> Mmm.. By manually checking magit log. It can provide extra highlight for
> things that have been changed and also moved around (which is more
> accurate than raw LOC count from git).
> 
> And I missed one of the aikrahguzar's commits. With f41befa, his
> contribution exceeds 15LOC.

I can see if he/she is willing to sign a copyright assignment form.

There's another contributor not reflected in the commit log, however. The code
that removes TeX markup was originally part of Ebib and contributed by Hugo
Heagren. I moved it to parsebib without thinking about proper attribution. I'll
ask him as well.



-- 
Joost Kremers
Life has its moments



[PATCH] org-attach.el: ID to path functions may return nil

2022-11-07 Thread Max Nikulin
Ihor, I played with my patch for some time and the only issue I have 
noticed is missed backslashes in a docstring.


On 05/10/2022 12:44, Ihor Radchenko wrote:


AFAIU, your version of `org-attach-dir-from-id' may sometimes return
nil, which is neither documented


"otherwise independently of TRY-ALL
value return the first non nil value."

indirectly assumes nil. It may be made more prominent.


nor expected by the callers.


I see 2 direct callers and I am not aware of any problem with them.


In particular, `org-attach-dir-get-create' will throw unhelpful "No
attachment directory is associated with the current node" error.


* H short
:PROPERTIES:
:ID:   ec
:END:

if: No attachment directory is associated with the current node, adjust 
‘org-attach-id-to-path-function-list’


I do not think this message is unhelpful.


`org-attach-dir' appears to handle nil return value fine.
From 19e51a0112353a377deef64a83c02c5ee393a15d Mon Sep 17 00:00:00 2001
From: Max Nikulin 
Date: Mon, 7 Nov 2022 23:48:02 +0700
Subject: [PATCH] org-attach.el: ID to path functions may return nil

* lisp/org-attach.el (org-attach-dir-from-id): Ignore nil values
returned by entries from `org-attach-id-to-path-function-list'.
(org-attach-dir-get-create): Update error message to suggest
customization of `org-attach-id-to-path-function-list'.
(org-attach-id-to-path-function-list): Add to the docstring examples
how to handle unusual IDs.
(org-attach-id-uuid-folder-format, org-attach-id-ts-folder-format):
Return nil if ID is too short.
(org-attach-id-fallback-folder-format): New function that may be added
as the last element of `org-attach-id-path-function-list' to handle
unexpectedly short IDs.

Earlier an obscure error like 'org-attach-id-ts-folder-format: Args out
of range: "ftt", 0, 6' was signalled in the case of unexpectedly short
ID.

Reported by Janek F 
https://list.orgmode.org/KC8PcypJapBpJQtJxM0kX5N7Z0THL2Lq6EQjBMzpw1-vgQf72egZ2JOIlTbPYiqAVD4MdSBhrhBZr2Ykf5DN1mocm1ANvvuKKZShlkgzKYM=@pm.me
---
 lisp/org-attach.el | 69 +-
 1 file changed, 44 insertions(+), 25 deletions(-)

diff --git a/lisp/org-attach.el b/lisp/org-attach.el
index ef183474e..f615e757a 100644
--- a/lisp/org-attach.el
+++ b/lisp/org-attach.el
@@ -166,18 +166,27 @@ When set to `query', ask the user instead."
   "Translate an UUID ID into a folder-path.
 Default format for how Org translates ID properties to a path for
 attachments.  Useful if ID is generated with UUID."
-  (format "%s/%s"
-	  (substring id 0 2)
-	  (substring id 2)))
+  (and (< 2 (length id))
+   (format "%s/%s"
+   (substring id 0 2)
+   (substring id 2
 
 (defun org-attach-id-ts-folder-format (id)
   "Translate an ID based on a timestamp to a folder-path.
 Useful way of translation if ID is generated based on ISO8601
 timestamp.  Splits the attachment folder hierarchy into
 year-month, the rest."
-  (format "%s/%s"
-	  (substring id 0 6)
-	  (substring id 6)))
+  (and (< 6 (length id))
+   (format "%s/%s"
+   (substring id 0 6)
+   (substring id 6
+
+(defun org-attach-id-fallback-folder-format (id)
+  "May be added last to `org-attach-id-path-function-list'.
+A fallback as \"__/ID\" directory for the case when user
+changed ID value to a string too short for `org-attach-id-ts-folder-format'
+and other functions."
+  (format "__/%s" id))
 
 (defcustom org-attach-id-to-path-function-list '(org-attach-id-uuid-folder-format
 		 org-attach-id-ts-folder-format)
@@ -185,7 +194,17 @@ year-month, the rest."
 The first function in this list defines the preferred function
 which will be used when creating new attachment folders.  All
 functions of this list will be tried when looking for existing
-attachment folders based on ID."
+attachment folders based on ID.
+
+Add `org-attach-id-fallback-folder-format' to the end if you edit
+IDs to short value, but you can not implement a better variant of
+layout.  Consider something like the following as first element instead
+
+(defun my/attach-id-custom-folder-format (id)
+ (unless
+  (or (string-match-p \"[0-9a-f]=\\{8}(?:-[0-9a-f]{4})=\\{3}-[0-9a-f]=\\{12}\" id)
+  (string-match-p \"[0-9]=\\{8}T[0-9]=\\{6}\\.[0-9]=\\{6}\" id))
+  (format \"important/%s/%s\" (substring id 0 1) (substring id 1"
   :group 'org-attach
   :package-version '(Org . "9.3")
   :type '(repeat (function :tag "Function with ID as input")))
@@ -387,7 +406,8 @@ If the attachment by some reason cannot be created an error will be raised."
 	 ((eq org-attach-preferred-new-method 'nil)
 	  (error "No existing directory.  DIR or ID property has to be explicitly created")
 (unless attach-dir
-  (error "No attachment directory is associated with the current node"))
+  (error "No attachment directory is associated with the current node, \
+adjust `org-attach-id-to-path-function-list'"))
   

[PATCH] rfc: using ert-deftest with side-effects

2022-11-07 Thread Leo Butler
Hello,

I am patching a bug in ob-octave.el (see attachment) involving the
creation of graphics files. The bug itself is easy to fix: a single line
in ob-octave.el ensures the special variable `ans' is bound, to prevent
Octave from exiting with a non-zero exit code.

However, I would like feedback/suggestions on writing such a
test. Issues include:

1. how to clean up the side-effects, including changes in the test
   buffer, filesystem and potentially creating an error buffer;
2. the general absence of similar tests (except in test-ob.el,
   test-ob/result-graphics-link-type-header-argument).

To address 1., I have wrapped the tests in an `unwind-protect' form to
ensure clean-up code gets run. The ERT manual does not suggest much
beyond this. At the moment, when the test is run, clean-up is being done
whether the test fails or passes.

I am unsure about 2. Is the absence of such tests because there is a
policy against them, or ...

Leo

diff --git a/lisp/ob-octave.el b/lisp/ob-octave.el
index 55926b789..f85b79fa2 100644
--- a/lisp/ob-octave.el
+++ b/lisp/ob-octave.el
@@ -91,7 +91,7 @@ end")
  (list
   "set (0, \"defaultfigurevisible\", \"off\");"
   full-body
-  (format "print -dpng %s" gfx-file))
+  (format "print -dpng %s\nans=%S" gfx-file gfx-file))
  "\n")
 		full-body)
 		  result-type matlabp)))
diff --git a/testing/examples/ob-octave-test.org b/testing/examples/ob-octave-test.org
index 9839d637e..0fc84bc26 100644
--- a/testing/examples/ob-octave-test.org
+++ b/testing/examples/ob-octave-test.org
@@ -46,10 +46,16 @@ ans = s
 
 
 * Graphical tests
-#+begin_src octave :results graphics :file chart.png
+  :PROPERTIES:
+  :ID:   b8b1d6a0-b7f6-49bd-8cb0-0c74f737332f
+  :END:
+
+Graphics file
+#+begin_src octave :results file graphics :file sombrero.png
 sombrero;
 #+end_src
 
+Graphics session
 #+begin_src octave :session
 sombrero;
 #+end_src
diff --git a/testing/lisp/test-ob-octave.el b/testing/lisp/test-ob-octave.el
index 78ce10214..bdc9befef 100644
--- a/testing/lisp/test-ob-octave.el
+++ b/testing/lisp/test-ob-octave.el
@@ -64,4 +64,22 @@
 (org-babel-next-src-block 5)
 (should (equal nil (org-babel-execute-src-block)
 
+(ert-deftest ob-octave/graphics-file ()
+  "Graphics file. Test that link is correctly inserted and graphics file is created (and not empty). Clean-up side-effects."
+  (org-test-at-id "b8b1d6a0-b7f6-49bd-8cb0-0c74f737332f"
+(org-babel-next-src-block)
+(org-babel-execute-src-block)
+(unwind-protect
+(prog1
+(and (should (search-forward "[[file:sombrero.png]]" nil nil))
+ (should (file-readable-p "sombrero.png"))
+ (should (let ((size (nth 7 (file-attributes "sombrero.png"
+   (> size 0)))
+ (should (not (get-buffer "*Org-Babel Error Output*")
+  ;; clean-up
+  (delete-file "sombrero.png")
+  (when (get-buffer "*Org-Babel Error Output*")
+(kill-buffer "*Org-Babel Error Output*"))
+  (revert-buffer t t
+
 (provide 'test-ob-octave)


Re: [PATCH] Re: Maxima code blocks does not work in windows revisited

2022-11-07 Thread Leo Butler
On Sun, Nov 06 2022, Ihor Radchenko  wrote:

> Leo Butler  writes:
>
>>> I do not have a Windows machine to test and not motivated enough to
>>> try Emacs in wine.
>>
>> Max, a minor modification of the test you sent earlier shows that when
>> system-type is ms-dos, the placement does not matter (the command-line
>> is the same); but for gnu/linux, placement matters and Eric is right
>> (the command-lines are not the same and the dollar sign needs to be
>> escaped).
>>
>> I have attached a patch that puts the dollar sign in the right place for
>> both. The existing tests pass when running 'make test'.
>
> Thanks for your contribution!
> Applied onto main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=9abf1b5167e94291eee7c1400277ed55993106f9
>
> You are now also listed as an Org mode contributor.
> https://git.sr.ht/~bzg/worg/commit/8750cbeccf4283be5ec7078f635f8328b2cbee09

Thanks, Ihor.
Leo


Re: [BUG] ob-doc-maxima.org and ob-maxima.el

2022-11-07 Thread Leo Butler
On Sat, Nov 05 2022, Ihor Radchenko  wrote:

> Leo Butler  writes:
>
>> I believe the attached patch fixes all the problems that you saw with
>> the previous versions.
>
> Thanks!
> Applied onto master.
> https://git.sr.ht/~bzg/worg/commit/c1440ba5f98634adf08209631d305c1814fb7f9a

Thanks, Ihor. I can see the new page already.

https://orgmode.org/worg//org-contrib/babel/languages/ob-doc-maxima.html

Best,
Leo


Re: Interest in an Org video meetup?

2022-11-07 Thread Sacha Chua
On Mon, Nov 7, 2022, 07:42 Russell Adams  wrote:

Does anyone know an open conferencing solution that allows smaller
> workgroups within a larger unit?
>

BBB has breakout rooms. I haven't experimented with them, but it looks like
you can set them up so that people can join the one they want, be randomly
assigned, or be manually assigned to one.
https://support.blindsidenetworks.com/hc/en-us/articles/360024516512-Create-and-manage-breakout-rooms
describes features and limitations. Might be something to play with on
bbb.emacsverse.org? Maybe we'll give it a try at EmacsConf too, like having
a general hangout during lunch break. Might be fun!

Sacha


Re: Interest in an Org video meetup?

2022-11-07 Thread Russell Adams
On Mon, Nov 07, 2022 at 12:08:32PM +, Ihor Radchenko wrote:
> Russell Adams  writes:
>
> >> For the sake of the talk, it would have to be worked out a bit sooner 
> >> actually.
> >> I’ll most likely be submitting a recording next weekend.
> >
> > I hadn't intended this to conflict with anything else. I was hoping to
> > start a routine meeting, and like I said my time was constrained where
> > I hadn't started yet.
> >
> > Would it be better to wait and schedule something after Emacsconf?
>
> Sorry, I think made a false impression in my message.
> I just thought that Emacsconf could be great opportunity to invite wide
> audience to these meetings. But we need to be sure that the meetings are
> going to happen---there is no point announcing a meeting that will not
> happen.
>
> There is no need to postpone anything. If you can start regular meetings
> earlier, it will be great.

One of my concerns is the format. I used to goto user groups
frequently, and we could break up into smaller groups working on many
things.

On the other hand, tools like BBB or Jitsi tend to be best for a
presenter and an audience.

I'm ok with prepping a presentation and a sample org file or two, and
answering questions in a group setting.

Does anyone know an open conferencing solution that allows smaller
workgroups within a larger unit?

--
Russell Adamsrlad...@adamsinfoserv.com
https://www.adamsinfoserv.com/



Re: Interest in an Org video meetup?

2022-11-07 Thread Ihor Radchenko
Russell Adams  writes:

>> For the sake of the talk, it would have to be worked out a bit sooner 
>> actually.
>> I’ll most likely be submitting a recording next weekend.
>
> I hadn't intended this to conflict with anything else. I was hoping to
> start a routine meeting, and like I said my time was constrained where
> I hadn't started yet.
>
> Would it be better to wait and schedule something after Emacsconf?

Sorry, I think made a false impression in my message.
I just thought that Emacsconf could be great opportunity to invite wide
audience to these meetings. But we need to be sure that the meetings are
going to happen---there is no point announcing a meeting that will not
happen.

There is no need to postpone anything. If you can start regular meetings
earlier, it will be great. 

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



Re: Interest in an Org video meetup?

2022-11-07 Thread Sacha Chua
Let's pick a Saturday one or two weeks after EmacsConf. Then we can
announce it either during Timothy's talk or during the live Q after
Timothy's talk in case the details don't get ironed out this weekend.
People can share what they picked up at the conference, and I can show the
Org files I use to manage EmacsConf behind the scenes. (Babel, SVG, mail
merge, todo state hooks, ...)

I am probably more available at 8 AM EST than in the afternoon (kiddo likes
to sleep in), but I might be able to swing 1-3 PM EST especially if it'll
be Dec 17 instead of Dec 10. Would either Dec 10 or 17 work for anyone, and
can I get away with 8 AM (good for Europe and Asia, doable for Eastern,
tough for Pacific time) or do we need 1-3pm EST?

Sacha

On Mon, Nov 7, 2022, 06:29 Russell Adams  wrote:

> On Mon, Nov 07, 2022 at 01:28:29PM +0800, Timothy wrote:
> > Hi Ihor,
> >
> > > To clarify, Timothy’s presentation is going to be in December.
> > > It would be great if you finalize how committed you can be to this by
> > > then. Both from technical point of view and from your free time
> > > availability.
> >
> > For the sake of the talk, it would have to be worked out a bit sooner
> actually.
> > I’ll most likely be submitting a recording next weekend.
>
> I hadn't intended this to conflict with anything else. I was hoping to
> start a routine meeting, and like I said my time was constrained where
> I hadn't started yet.
>
> Would it be better to wait and schedule something after Emacsconf?
>
>
> --
> Russell Adamsrlad...@adamsinfoserv.com
> https://www.adamsinfoserv.com/
>
>


Re: Interest in an Org video meetup?

2022-11-07 Thread Russell Adams
On Mon, Nov 07, 2022 at 01:28:29PM +0800, Timothy wrote:
> Hi Ihor,
>
> > To clarify, Timothy’s presentation is going to be in December.
> > It would be great if you finalize how committed you can be to this by
> > then. Both from technical point of view and from your free time
> > availability.
>
> For the sake of the talk, it would have to be worked out a bit sooner 
> actually.
> I’ll most likely be submitting a recording next weekend.

I hadn't intended this to conflict with anything else. I was hoping to
start a routine meeting, and like I said my time was constrained where
I hadn't started yet.

Would it be better to wait and schedule something after Emacsconf?


--
Russell Adamsrlad...@adamsinfoserv.com
https://www.adamsinfoserv.com/



Re: [PATCH] oc-csl: Improve LaTeX bibliography formatting

2022-11-07 Thread András Simonyi
Dear All,

On Mon, 7 Nov 2022 at 03:47, Ihor Radchenko  wrote:

>  Please, document the new customization in ORG-NEWS.

Dear Ihor, thanks for the comments! I'm going to update the NEWS file
shortly in a new version of the patch.

> Also, it would be nice to describe CSL usage and tweaks in the manual.

Time permitting I may try to add something, but wouldn't it be a
problem if the CSL export processor was discussed in much more detail
than the others?
I was also thinking about providing a list of available citation
substyles but I do not want to make the manual very unbalanced.

> I have two comments here:
> 1. Where are all these new commands coming from? They are not used
>directly in the code. Are you tweaking citeproc.el output this way? May
>it be better to use customizations provided by citeproc.el itself?

Yes, the citeproc org-latex formatter, which I added specifically for
Org, uses these commands in the LaTeX code produced for the
bibliography. As citeproc doesn't have customizable variables by
design (if I recall correctly, the only exception is 2 hooks), and
oc-csl already had some variables concerned with very similar
formatting settings (org-cite-csl-latex-hanging-indent,
org-cite-csl-html-hanging-indent,
org-cite-csl-html-label-width-per-char) I think it is more consistent
to have the new ones also in Org.

> 2. You are declaring this variable as defcustom, but it is not clear
>what is going to happen if the user changes it. It is not how to
>change this template in meaningful ways either.

Right, I can try to detail a bit in the docstring what type of
commands and environments have to be provided by the preamble (are
expected by citeproc). I tried to follow Timothy's handling of the
ox-latex engraved preamble, but a simpler alternative would be to
treat it simply as a constant template, at least for the time being --
WDYT?

best wishes,
András

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



Re: View next 7 days of agenda, not next week

2022-11-07 Thread Ihor Radchenko
Renato Pontefice  writes:

> I do not read the Org Manual. I’ve just reach it and found Agenda part of it. 
> But I find just things that do not interest. Is it possible to have what am I 
> asking? If yes, what can I look for in Org manual?

I think that I need to clarify a bit why you are getting responses like
"check yourself" now.

You have been asking a number of questions recently.

Asking questions is fine here, and we are willing to help, especially for
newcomers. However, your messages did not look like you took time to try
finding the answer yourself. You also did not formulate some of your
questions clearly.

I suggest you to read http://www.catb.org/esr/faqs/smart-questions.html
It explains the situation in details and provides some guidelines on how
to ask questions in technical forums and communities.

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



Re: View next 7 days of agenda, not next week

2022-11-07 Thread Ihor Radchenko
Renato Pontefice  writes:

> I do not read the Org Manual. I’ve just reach it and found Agenda part of it. 
> But I find just things that do not interest. Is it possible to have what am I 
> asking? If yes, what can I look for in Org manual?

11.3.1 Weekly/daily agenda
org-agenda-start-day
You can set it to "+0d".

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



Re: View next 7 days of agenda, not next week

2022-11-07 Thread Renato Pontefice
I do not read the Org Manual. I’ve just reach it and found Agenda part of it. 
But I find just things that do not interest. Is it possible to have what am I 
asking? If yes, what can I look for in Org manual?

Thank you

Renato

> Il giorno 5 nov 2022, alle ore 23:57, Quiliro Ordóñez  ha 
> scritto:
> 
> El 2022-11-05 15:51, Renato Pontefice escribió:
>> With this command
>> (org-agenda-list)
>> (delete-other-windows)
>> 
>> My org-mode open with the present week days appointment and TODO
>> 
>> I would open with next 7 days view every day, not just on Monday.
>> Is it possible?
> 
> Did you read the Org manual?
> 




Re: Interest in an Org video meetup?

2022-11-07 Thread Timothy
Hi Ihor,

> To clarify, Timothy’s presentation is going to be in December.
> It would be great if you finalize how committed you can be to this by
> then. Both from technical point of view and from your free time
> availability.

For the sake of the talk, it would have to be worked out a bit sooner actually.
I’ll most likely be submitting a recording next weekend.

All the best,
Timothy


Re: [PATCH] Prevent blocked tasks from being archived

2022-11-07 Thread Ihor Radchenko
Ankit Raj Pandey  writes:

> When org-archive-mark-done is enabled, org silently fails on setting the
> TODO state of the archived headline to DONE if the task is blocked.
>
> This patch changes that behavior so the headline is prevented from being
> archived in the first place. Instead, org displays a message about why
> the task is blocked (this message comes from org-todo).

Thanks for the patch, and sorry for the late reply.

I see that you moved changing the todo state code before we switch to
the archive buffer. It is not safe. If something goes wrong during
archive process after changing the todo state, the todo will not be
recovered even though archiving fails.

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



Re: [PATCH] Document custom org agenda functions

2022-11-07 Thread Ihor Radchenko
thecashewtrader  writes:

> +* User Defined Functions
> +** Function Signature
> +User defined functions should:
> +
> +- Optionally accept one parameter i.e. the =match= variable. The Org agenda 
> dispatch function will call the user-defined function with one parameter 
> representing the =match= component from the agenda definition. In other 
> words, ~(udf/test "Hello")~ in =org-agenda-custom-commands= will result in a 
> function call of ~udf/test~ with an argument of ="Hello"=.
> +
> +- Prepare a buffer to write the agenda information to using 
> ~org-agenda-prepare~.
> +
> +- Handle setting a unique buffer name for the cases where 
> =org-agenda-sticky= has a value of =t=.
> +
> +- Honor the setting of =org-agenda-overriding-header= and insert that text 
> into the agenda buffer. This can be done using the macro 
> ~org-agenda--insert-overriding-header~.
> +
> +- Insert into the buffer the desired contents, accounting for also setting 
> text properties.
> +
> +- Call ~org-agenda-finalize~ and ~(setq buffer-read-only t)~

Thanks for the patch, and sorry for the late reply.

I am not sure if this explanation is useful.

Yes, it kind of works and also inserts text into agenda. However, the
inserted text will not allow the usual agenda interaction. One would
also need to set various text properties pointing to an Org heading in
order to make the inserted lines interactive.

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