> Yeah, org-store-link overloads ARG Exactly!
> I think that, when negating org-context-in-file-links, the function should > check whether a single C-u was given rather than just checking if ARG is > non-nil. Seems to be a reasonable solution to me. So would you go ahead and make the change, or, would more people need to agreed on this solution? > If someone uses C-u C-u to fall back to core Org functions, I don't see any > reason to assume that they also want to reverse their > org-context-in-file-links preference. Maybe! Thanks, York On Sat, May 20, 2017 at 6:55 PM, Kyle Meyer <k...@kyleam.com> wrote: > York Zhao <gtdplatf...@gmail.com> writes: > > > However, the biggest problem I'm having now is that once I loaded > > org-git-link.el, I'm forced to always store links linking to git > repository > > which is not always I want because I also need to be able to store links > > linking to the files in the working directory instead of in the git > > repository. > > > > I'm aware of the 'C-u C-u' prefix of `org-store-link', however, by the > > current design, using 'C-u C-u' negates `org-context-in-file-links', > i.e., > > the link would be stored without embedding the text to search for. > > Yeah, org-store-link overloads ARG, and there seems to be an undesirable > interaction here. > > > Is it possible to make `org-store-link' able to skip the link storing > > functions without touching `org-context-in-file-links'? > > I think that, when negating org-context-in-file-links, the function > should check whether a single C-u was given rather than just checking if > ARG is non-nil. If someone uses C-u C-u to fall back to core Org > functions, I don't see any reason to assume that they also want to > reverse their org-context-in-file-links preference. > > -- > Kyle >
