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 770548 - Information for command line switches
Information for command line switches
Product: epiphany
Classification: Core
Component: Documentation
git master
Other Linux
: Normal enhancement
: ---
Assigned To: Maintainers of Gnome user documentation
Epiphany Maintainers
Depends on:
Reported: 2016-08-29 12:39 UTC by Alexandre Franke
Modified: 2018-08-03 20:51 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Alexandre Franke 2016-08-29 12:39:12 UTC
I discovered with `epiphany --help` that there are several hidden modes, but I can't tell the difference between them. These are the private, incognito, and netbanking modes.
Comment 1 Michael Catanzaro 2016-08-29 12:56:47 UTC

-p is --profile mode, it means you can store user data in a separate profile directory, so you can have different "user accounts" in your browser. Put the directory under /tmp and you have the "guest windows" that Allan wants.

Incognito mode avoids saving evidence of your browsing on disk (history, cache, cookies, etc.). netbank mode is a synonym that probably causes more confusion than it's worth.
Comment 2 Alexandre Franke 2016-08-29 13:27:05 UTC
-p claims to be --private-instance and is listed as a different entry than --profile
Comment 3 Michael Catanzaro 2016-08-29 16:17:23 UTC
(In reply to Alexandre Franke from comment #2)
> -p claims to be --private-instance and is listed as a different entry than
> --profile

Heh, I didn't know about this mode. It is a shorthand for --profile-mode with the  profile directory under /tmp
Comment 4 GNOME Infrastructure Team 2018-08-03 20:51:48 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: