or to [/mere brainstorm alert/] get really fancy, to be able to mark a
place where links are to be inserted [perhas to become a plain list or
so] then collect llinks from all over, then hit store and they all go
to the place you marked. crash-proof.
On 6/29/23, Samuel Wales wrote:
> although i
although i just store and insert now, i'd also welcome the ability to
collect links from various places and have them someplace like a
register where they can be pasted all at once. or even edit the list
in the register, clear it, etc.
On 6/29/23, Ihor Radchenko wrote:
> Anthony Carrico
Matt writes:
> Changes have been pushed
Thanks!
For future reference:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=1b5451a10504ad5d17453e15bba5ea1cb0394399
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=9da248ccd2e2fb86a37009bb0e672cb8419dc30c
Changes have been pushed
Matt writes:
> > "Convert region" may be still confusing. Maybe something like
> > "Convert Org region to other markup syntax"?
>
> How about renaming the section to "Export Region"?
Reasonable.
> > We can also create more intuitive function aliases.
>
> How about
On Thu, 29 Jun 2023 12:24:12 +0200 Ihor Radchenko wrote ---
> > - Section 13.18: Export in Foreign Buffers
> >
> > The section uses the term "foreign buffer" without providing a definition.
> >
> > Proposed solution: Change wording from "foreign buffers" to "Convert
> > Region"
On 6/29/23 11:54, Ihor Radchenko wrote:
You can set :store property for "file" links in `org-link-parameters' to
adjust for your personal use case.
That is good advice.
--
Anthony Carrico
Hi Ihor,
Thank you for the feedback.
Ihor Radchenko writes:
+ ;; Apply WRITE-BACK function on edit buffer contents.
+ (goto-char (point-min))
+ (when (functionp write-back) (save-excursion (funcall write-back)))
(set-marker marker nil
`save-excursion' is no longer
Anthony Carrico writes:
> On 6/29/23 09:20, Ihor Radchenko wrote:
>> Sure. And if it were a plain file link, there would be no reason to
>> assign TITLE as description. Because the link would be to a generic line
>> in file.
>
> What? The title is the perfect description for the file!
That's
On 6/29/23 09:20, Ihor Radchenko wrote:
Sure. And if it were a plain file link, there would be no reason to
assign TITLE as description. Because the link would be to a generic line
in file.
What? The title is the perfect description for the file!
I would say that 90% of the links in my org
Solved, thanks! :-)
;;;_ borrar todas las etiquetas al cambiar el estado a HECHO
(defun borrar-etiquetas-tareas-hechas (plist)
"Borra todas las etiquetas al cambiar una tarea a =HECHO=."
(when (eq (plist-get plist :type) 'todo-state-change)
(when (string= (plist-get plist :to) "HECHO")
Anthony Carrico writes:
> #+begin_example
> [[id:5f4cdb46-d18d-41bb-914e-da7faa12][test org title link]]
> #+end_example
>
> ...hmm, you are correct that this option does add the proper default
> description, but this is not a just plain file link anymore.
Sure. And if it were a plain file
Anthony Carrico writes:
>> Makes sense. It is a +1 for a defcustom.
>> Although I still believe that we should change the current default, even
>> if leaving an option to fall back to previous behaviour.
>
> I don't think there is much reason to complicate the interface with a
> defcustom. The
On 6/28/23 16:16, Ihor Radchenko wrote:> It has been added back in Org 9.5.
Thanks, I'm on 9.5.5, so I can test it...
You can set `org-id-link-to-org-use-id' to non-nil (4.5 Handling Links).
Then, Org will store link to current file/heading instead of more
generic link. Latest version of Org
On 6/29/23 06:28, Ihor Radchenko wrote:
Samuel Wales writes:
if you move the recent one to top of list, that would work for my
mindless store/insert, but it might not work for a user who has
carefully cultivated a set of links that are all to be inserted, or
such. although idk if the
Max Nikulin writes:
>>> Could it be possible to make inline comments (# something like this) ?
> ...
>> Previous discussion:
> ...
>
> I think, it is time to add a FAQ entry, see the attachment.
The proposed FAQ entry is overwhelming. It would work fine as a blog,
but not as a quick answer to a
Samuel Wales writes:
> i am not sure i am using store/insert to their full actual or
> potential potential.
>
> if you move the recent one to top of list, that would work for my
> mindless store/insert, but it might not work for a user who has
> carefully cultivated a set of links that are all
Matt writes:
> - Section 13.18. 1: Bare HTML may be better placed under Section 13.9 HTML
> Export. The information in this section appears unrelated to Exporting in
> non-Org buffers. In fact, the settings given for a minimal HTML export do
> not apply when converting a region. For
18 matches
Mail list logo
