GNU-devel ELPA - org-transclusion

* Under development (as of 2024-12-31)

  - Fixes ::

    fix: #177 Infinite loop when saving buffer with transclusions

         Fixing a long-lasting (issue open since March 2023, but it had been an
         known issue before it) issue that was difficult to reproduce.

         The fix is to stop using the text-properties of the transclusion that
         hold markers of beginning and ending points of itself, which is meant
         to remember and indicate its own the location; or the range of "this"
         transclusion at point. The text-properties are named
         `org-transclusion-beg-mkr' and `org-transclusion-end-mkr'. They are
         replaced with use of a new text-property `org-transclusion-id' and
         function `org-transclusion-at-point'. This new function uses
         `prop-match' with `org-transclusion-id' to identify the range of "this"
         transclusion at point only when it is needed, thus eliminating the need
         for memorizing it as a pair of markers.

         Stable reproduction was achieved and recorded in a comment to the GitHub
         issue at
         https://github.com/nobiot/org-transclusion/issues/177#issuecomment-2108453402.

         A quick summary of the design hitherto and how the infinite loop occurs
         is as follows:

         [Fact / design of org-transclusion]

         - Each transclusion has text-properties org-transclusion-beg-mkr and
           org-transclusion-end-mkr.

         - They hold markers to keep track of where the transclusion begins and
           ends.

         [Now what happens]

         - In some combination of undo and buffer-save with transclusions, the
           markers can temporarily point to non-existing locations in the
           buffer.

         - If the garbage collection happens to run at this moment, it will
           sweep these pointers. Now they end up pointing to start of the buffer
           (point 1).

* 1.4.0 (2024-05-20)

  - Features ::

    Transclude content over network protocols like http:// (with
    org-transclusion-http: https://git.sr.ht/ushin/org-transclusion-http) and
    hyper:// (with hyperdrive-org-transclusion:
    https://git.sr.ht/~ushin/hyperdrive-org-transclusion).  Splitting
    org-transclusion-add into two parts enables functions in
    org-transclusion-add-functions to be asynchronous.

    - chg: #213 Allow making transclusion links from any protocol link
    - refactor: #209 Split -add-payload from -add to enable async transclusion

    add :things-at-point (or :thingatpt) property for transcluding
    source and other non-org text files. Both property names are synonym
    with each other and work in the same way.

    add org-block-live-sync

    - Command 'org-transclusion-live-sync-start' now can start live sync
      when

      1) transcluding a source code text file
      2) into org src block with the ':src' property in #+transclude

      Example: #+transclude: [[python-1.py]]  :src python

    add org-transclusion-detach

    - New command 'org-transclusion-detach' can be used on the
      transclusion at point. It turns it into a normal, edtitable text
      content.

      You can undo this operation.

      In addition, you can press 'C-d' directly on the transclusion at
      point to detach it. This is because the command is bound to 'C-d'
      by default in 'org-transclusion-map'.

    - 'org-transclusion-refresh' now accepts universal argument such as
      'C-u M-x org-transclusion-refresh' and detaches the transclusion
      at point.

      You can undo this operation.

    - 'org-transclusion-add' now accepts universal argument such as 'C-u
      M-x org-transclusion-add' and copies the source content rather
      than transclude it.

      You can undo this operation.

    - Limitation: Undo detach does not add the overlay back on the
      source. This should not break any feature. You can safely refresh
      the transclusion and recover the source overlay. You can also
...
...