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 154235 - Enhancement: add a --new-process flag to be able to run 2 yelps
Enhancement: add a --new-process flag to be able to run 2 yelps
Status: RESOLVED FIXED
Product: yelp
Classification: Applications
Component: General
2.6.x
Other Linux
: Normal enhancement
: ---
Assigned To: Shaun McCance
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2004-10-01 12:10 UTC by Adrian Custer
Modified: 2006-06-11 18:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adrian Custer 2004-10-01 12:10:38 UTC 
It would be useful occaisionally to examine the rendering of two versions of the
same doc. The current yelp simply grabs the existing parse.

A --new-process command line flag (like gnome-terminal's --disable-factory)
would call a different yelp than the one already running and ensure that the
file was parsed separately in this process
Comment 1 Shaun McCance 2005-01-09 22:07:21 UTC 
That sounds kind of hackish.  Yelp has reload functionality now, so you can
watch the effect of your source changes pretty easily.  Is that enough?
Comment 2 Adrian Custer 2005-01-09 23:23:45 UTC 
I aggree this is minor, only useful for authors. 

The idea is to be able to see two different renderings at once. For example,

edit a file -> open yelp... gives the original view (keep this open for later
comparison)

edit some more -> open yelp --new-process ... gives a new view and the two can
be compared. 

reload doesn't provide this ability because yelp will simply update to the new view.

However, you've got better things to do with your time; close this if you don't
feel like doing it.

--adrian
Comment 3 Don Scorgie 2006-06-11 18:41:40 UTC 
Yelp in CVS HEAD now has a -p flag (or --private-session) that when set, won't connect to currently running instances, keeping everything private.

This should fix this bug.  Closing.