On 06.01.2010 10:05, Carsten Dominik wrote:
Would you like to work on a patch that allows interpreting page numbers
for external applications?
I'll definitely take a stab at it and see how far I get while learning
more about elisp along the way. I will post to the mailing list if I
make
On Jan 6, 2010, at 12:07 PM, Jan Böcker wrote:
On 06.01.2010 10:05, Carsten Dominik wrote:
Would you like to work on a patch that allows interpreting page
numbers
for external applications?
I'll definitely take a stab at it and see how far I get while learning
more about elisp along the
Hi,
during following this thread I noticed one problem with the page and line-
number concept
- file:~/some-file.txt::23some-file.txt, line 23
A txt-file may have no clear page boarders. Thus only a line number might make
sens
- file:~/document.pdf:4 document.pdf, page 4
A
I am not sure if it makes sense to handle more that a page number, really.
I have thought about this again and concluded that the approach in my
first post is, indeed, over-engineered. I also believe the approach
proposed in this post to be flexible enough to handle some extensions.
On
If you need the syntax to be more general, take a look at extensible
syntax on this list.
--
Q: How many CDC scientists does it take to change a lightbulb?
A: You only think it's dark. [CDC has denied ME/CFS for 25 years]
=
Hello List,
During the discussion in the protocol for PDFs? thread, I realized
that docview: links are an almost exact copy of file: links, the only
single difference being that file: takes a line number and docview:
links take a page number.
Up until now, (docview:) links to PDF files have been
