On Tue, Oct 12, 2021 at 7:28 PM John Kitchin wrote:
>
> I am not sure it really fits the model of the exporters that are in org,
> since it is basically just a pre-processing hook.
[snip]
> It also is (IMO) a part of org-ref since it uses the links that are defined
> in org-ref. I see it as
I am not sure it really fits the model of the exporters that are in org,
since it is basically just a pre-processing hook. I don't think there are
any exporters in org that rely on that, e.g. you can't just C-c C-e choose
a backend and export with a pre-processing hook. It doesn't make sense to
On Tue, Oct 12, 2021 at 5:16 PM John Kitchin wrote:
>
> I think the existing link capability of org-mode is completely adequate for
> cross-references. LaTeX exports are almost completely covered in org-ref. I
> made a refproc
>
I think the existing link capability of org-mode is completely adequate for
cross-references. LaTeX exports are almost completely covered in org-ref. I
made a refproc (
https://github.com/jkitchin/org-ref/blob/org-ref-3/org-ref-refproc.el) that
provides similar export behavior for other backends
Can we go back to this question of whether internal links are adequate
for cross-references, and if not, what's missing?
On Fri, Aug 13, 2021 at 11:22 AM Eric S Fraga wrote:
>
> Hello John & co.,
>
> I need to chime in when it comes to the UI:
>
> On Thursday, 12 Aug 2021 at 13:19, John Kitchin
Hello John & co.,
I need to chime in when it comes to the UI:
On Thursday, 12 Aug 2021 at 13:19, John Kitchin wrote:
> I would say the UI that I like, have used for many years, and is the
> default of org-ref is:
>
> 1. You type C-c ] to insert a citation
> 2. You type C-u C-c ] to insert a
On Thu, Aug 12, 2021 at 1:19 PM John Kitchin wrote:
> so, I guess I am in agreement that it is option 2, and that there needs to be
> a single entry point for each one.
+1
So I guess open questions:
1. a new syntax that mirrors cite (and accompanying new
cross-reference element?), per
> As I have thought about this more, the line between citations and
> > cross-references has blurred. In org-ref, they were handled the same
> > way, with org-links (although each link had its own export function).
> > For both cites and refs, the links are just pointers, and in both cases
> > it
On Wed, Aug 11, 2021 at 1:31 PM John Kitchin wrote:
...
> > It's just there needs to be some way to distinguish among types of
> > targets, I think.
>
> At the risk of repeating myself, I don't think this is true.
Just to clarify ...yes, I agree with you; I wrote that before the
subsequent
"Bruce D'Arcus" writes:
> Here's a recent subthread on this question:
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2021-07/msg00233.html
>
> At the end of that discussion, my argument against using citations for
> cross-references:
>
> 1. Cross-references are not citations, neither
That'd be my preferred solution, with (notwithstanding name overlap with
org-ref) an org-ref-insert entry point.
On Wed, Aug 11, 2021, 12:10 PM Timothy wrote:
> Hi Bruce, John,
>
> Regarding the issues with overloading [cite:@] syntax, would it be too
> much to
> introduce [ref:@] which would
Hi Bruce, John,
Regarding the issues with overloading [cite:@] syntax, would it be too much to
introduce [ref:@] which would function identically, but deal with references?
All the best,
*Timothy*
On Wed, Aug 11, 2021 at 10:56 AM John Kitchin wrote:
> This is a bad idea to me. It is only a fuzzy link (what you call a typed
> internal link) if no one has defined it as an external link. As soon as that
> happens, then you will lose the export behavior defined for fuzzy links, and
> get
On Wed, Aug 11, 2021 at 10:32 AM Bruce D'Arcus wrote:
> On Wed, Aug 11, 2021 at 9:53 AM John Kitchin
> wrote:
>
> > > #+CAPTION: This is the caption for the next figure link (or table)
> > > #+NAME: fig:SED-HR4049
> > >
> > > [[./img/a.jpg]]
> > >
> > > Or some other metadata on the target?
>
On Wed, Aug 11, 2021 at 9:53 AM John Kitchin wrote:
> > #+CAPTION: This is the caption for the next figure link (or table)
> > #+NAME: fig:SED-HR4049
> >
> > [[./img/a.jpg]]
> >
> > Or some other metadata on the target?
>
> I don't think metadata on the target helps with the cases described
>
"Bruce D'Arcus" writes:
> On Wed, Aug 11, 2021 at 7:13 AM Bruce D'Arcus wrote:
>
>> Is there a workaround for this somehow, or an alternative that gets
>> the same thing in the end?
>
> Like, if not typing the link, type the target?
>
> From this example from org-mode manual, the "fig" in the
"Bruce D'Arcus" writes:
> Hi John,
>
> On Tue, Aug 10, 2021 at 8:58 PM John Kitchin wrote:
>
>> ... I would like what I call an orthogonal approach for cross-references,
>> orthogonal in the sense that it can coexist with org-ref, but not require
>> org-ref if you don't use it. The built in
On Wed, Aug 11, 2021 at 7:13 AM Bruce D'Arcus wrote:
> Is there a workaround for this somehow, or an alternative that gets
> the same thing in the end?
Like, if not typing the link, type the target?
>From this example from org-mode manual, the "fig" in the name keyword
could provide that type?
Here's a recent subthread on this question:
https://lists.gnu.org/archive/html/emacs-orgmode/2021-07/msg00233.html
At the end of that discussion, my argument against using citations for
cross-references:
1. Cross-references are not citations, neither conceptually, nor in
software
In general I like John's suggestion. Org link syntax can be made to do
nearly anything because it is possible to bind link actions to
arbitrary elisp functions (I have used them to create buttons that run
source blocks for some of my non-technical colleagues). The grouping
of cross references
Hi John,
On Tue, Aug 10, 2021 at 8:58 PM John Kitchin wrote:
> ... I would like what I call an orthogonal approach for cross-references,
> orthogonal in the sense that it can coexist with org-ref, but not require
> org-ref if you don't use it. The built in internal links like [[label]] lack
To preface this, let me note that I am looking for a way to replace org-ref
with a complete and orthogonal package for writing scientific papers with
citations and cross-references. (I can probably live without the glossary
and acronym support). The cross-references in org-ref were handled with
22 matches
Mail list logo
