App-FirefoxMultiAccountContainersUtils
view release on metacpan or search on metacpan
Related topics
In Google Chrome browser, profiles is what you would use to separate
sessions/cookies (and other things). Opening a URL in a specific profile
from the command-line is easier with Chrome:
% google-chrome --profile-directory="PROFILEDIRNAME" URL
where "PROFILEDIRNAME" is a directory name under the profiles directory,
typically "~/.config/google-chrome/" on Unix. You can use the
list-chrome-profiles (with option "-l") (from App::ChromeUtils) to list
Chrome profiles.
This function is not exported.
Arguments ('*' denotes required arguments):
* container* => *str*
(No description)
lib/App/FirefoxMultiAccountContainersUtils.pm view on Meta::CPAN
**Related topics**
In Google Chrome browser, profiles is what you would use to separate
sessions/cookies (and other things). Opening a URL in a specific profile from
the command-line is easier with Chrome:
% google-chrome --profile-directory="PROFILEDIRNAME" URL
where `PROFILEDIRNAME` is a directory name under the profiles directory,
typically `~/.config/google-chrome/` on Unix. You can use the
<prog:list-chrome-profiles> (with option `-l`) (from <pm:App::ChromeUtils>) to
list Chrome profiles.
MARKDOWN
args => {
%argspecopt_profile,
container => {
schema => 'str*',
completion => \&_complete_container,
req => 1,
lib/App/FirefoxMultiAccountContainersUtils.pm view on Meta::CPAN
B<Related topics>
In Google Chrome browser, profiles is what you would use to separate
sessions/cookies (and other things). Opening a URL in a specific profile from
the command-line is easier with Chrome:
% google-chrome --profile-directory="PROFILEDIRNAME" URL
where C<PROFILEDIRNAME> is a directory name under the profiles directory,
typically C<~/.config/google-chrome/> on Unix. You can use the
L<list-chrome-profiles> (with option C<-l>) (from L<App::ChromeUtils>) to
list Chrome profiles.
This function is not exported.
Arguments ('*' denotes required arguments):
=over 4
=item * B<container>* => I<str>
script/open-firefox-container view on Meta::CPAN
B<Related topics>
In Google Chrome browser, profiles is what you would use to separate
sessions/cookies (and other things). Opening a URL in a specific profile from
the command-line is easier with Chrome:
% google-chrome --profile-directory="PROFILEDIRNAME" URL
where C<PROFILEDIRNAME> is a directory name under the profiles directory,
typically C<~/.config/google-chrome/> on Unix. You can use the
L<list-chrome-profiles> (with option C<-l>) (from L<App::ChromeUtils>) to
list Chrome profiles.
=head1 OPTIONS
C<*> marks required options.
=head2 Main options
=over
( run in 1.568 second using v1.01-cache-2.11-cpan-64ef6c95b5d )