After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 613449 - Open file on a specific absolute page number
Open file on a specific absolute page number
Status: RESOLVED FIXED
Product: evince
Classification: Core
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Evince Maintainers
Evince Maintainers
: 604328 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-03-20 23:36 UTC by Juanjo Marín
Modified: 2010-04-01 11:05 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Fix #613449 open a file in a specific page number (absolute based, not label based) (1.69 KB, patch)
2010-03-20 23:39 UTC, Juanjo Marín 		none Details | Review

Description Juanjo Marín 2010-03-20 23:36:24 UTC 
Would it be possible to have a command line option to open a file in a specific page number (absolute based, not label based)?

Submitted via evince-list@gnome.org [1] by D M German <dmg@uvic.ca>

[1] http://mail.gnome.org/archives/evince-list/2010-March/msg00003.html
Comment 1 Juanjo Marín 2010-03-20 23:39:41 UTC 
Created attachment 156644 [details] [review]
Fix #613449 open a file in a specific page number (absolute based, not label based)

Author: D M German <dmg@uvic.ca>
Comment 2 Carlos Garcia Campos 2010-04-01 11:05:04 UTC 
There are several problems in the patch:

 - Page number shouldn't be 0 based, that's for internal use only, we always expose to user that first page is 1. Command line interface should be consistent with GUI. 

 - What happen if both -p and -i options are provided? Page label takes precedence, which I think is good, but global_dest is leaked. 

I've just fixed these issues and pushed the patch to git master. 

Thank you very much.
Comment 3 Carlos Garcia Campos 2010-04-01 11:05:42 UTC 
*** Bug 604328 has been marked as a duplicate of this bug. ***