Re: incorrect documentation for file-desc header argument?

Matt Huszagh writes: > Thanks for the clarification Kyle. I've attached a patch that I believe > clarifies the documentation to match the current behavior. Thank you. Applied (521d7f5fe), tweaking the commit message a bit to align more closely with the conventions described at

Re: incorrect documentation for file-desc header argument?

Kyle Meyer writes: > Yeah, that looks to be the intended result of that thread. That > thread's patch was applied with a58a4f0ad (new source block header > argument :filelinkdescr, 2012-03-27). However, shortly after, that > treatment was intentionally changed (670c7f31c, 2012-03-31): > > s

Re: incorrect documentation for file-desc header argument?

On Wednesday, 29 Jul 2020 at 01:03, Kyle Meyer wrote: > So, I'd say this is a documentation bug. Yes or else many of my org files would cease to work as intended! -- : Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-682-geac255

Re: incorrect documentation for file-desc header argument?

Matt Huszagh writes: > The org info documentation states > > The ‘file-desc’ header argument defines the description (see *note > Link Format::) for the link. If ‘file-desc’ has no value, Org uses > the generated file name for both the “link” and “description” parts > of the l

Re: incorrect documentation for file-desc header argument?

Matt Huszagh writes: > Hello, > > The org info documentation states > > The ‘file-desc’ header argument defines the description (see *note > Link Format::) for the link. If ‘file-desc’ has no value, Org uses > the generated file name for both the “link” and “description” parts >

incorrect documentation for file-desc header argument?

Hello, The org info documentation states The ‘file-desc’ header argument defines the description (see *note Link Format::) for the link. If ‘file-desc’ has no value, Org uses the generated file name for both the “link” and “description” parts of the link. However, if I evalu