pvsr / qbpm Goto Github PK

from-session always looks at {data_home}/qutebrowser. so there's no easy way to turn a session from a profile into a new profile.

Maybe it would be better to generate a directory from a template rather than mess around with copying and renaming trees.

Seems like it'd be pretty simple. If not, shell completions for pass might be a good reference.

I don't use either so I'm probably not going to put as much effort in as for fish, but completions for qbpm launch at least would be nice.

A window pops up that says "Error while listening to IPC server: QLocalServer::listen: Name error (error 2)".

I'm thinking there should be a couple different "modes" and that all other flags should be incidental.

• link-config -- default, symlink config excl. bookmarks, copy history
• copy-config -- same as link-config but copy instead
• ssb -- symlink some config files, add custom ssb config
• clone -- full backup, copy everything to another directory

Plus --launch for new and from-session.

This issue is for discussing auto-generating .desktop files which is listed as a possible future feature in the README.

I'm not sure if you care, but this project name conflicts with qpm, the Qt Package Manager:

https://repology.org/project/qpm/versions

qbpm has no conflicts.

(There's also a project named qp: https://formulae.brew.sh/formula-linux/qp )

Deletes a profile, pretty self-explanatory.

Hello!
My understanding is that qbpm supports applescript, rofi, dmenu and dmenu-wl.
Wofi is quite a popular launcher among users of wayland compositors, and from my understanding it's equivalent to rofi, similarly to how dmenu is to dmenu-wl

I'm really impressed with how well qpm integrates with rofi too, it's incredibly convenient, and a very well thought-out tool.

Apologies if it sounds like I am demanding, but I was wondering if wofi could be supported in the future, and if it's not currently planned, what would need to be done to enable its support.

Thank you for reading my inquiry!

On windows, qutebrowsers config.py is located in ~/AppData/Roaming/qutebrowser/config/config.py.
However qbpm sources ~/.config/qutebrowser/config.py.

If I type $ qbpm --profile-dir $MY_PROFILE_DIR launch and hit tab, the completion should list the profiles in $MY_PROFILE_DIR rather than the default profile location. See https://github.com/fish-shell/fish-shell/blob/ac428b23e540c2f6afd7f43129a20006192fdf38/share/completions/git.fish for an example of parsing the command-line options within the completion. This could be done by a qbpm complete command which would have the advantage of using the full profile dir resolution and thus also respecting the profile dir environment variable and the config file if I ever add one.

Hi. This is a great idea. I had been using multiple profiles just with wrapper scripts. qpm fits right in into my workflow.

What do you think about adding a qpm list command?

You can't be a real, grown-up unix tool without having a man page. Right now everything has to be documented in --help or the readme which don't have as much room for the nitty-gritty details.

qbpm launch --tmp maybe? It would be cool to have a way to convert the temporary profile to a full one somehow. You could alias qutebrowser to that to achieve something similar to dwb and this script (I think, I haven't used either).

For Qute instances to be seen as completely seperate apps by the windowing system, they should set a unique WM_CLASS under X11 and a custom app_id under Wayland. qutebrowser supports both currently in Git.

To set a custom WM_CLASS that will be recognized by X11, you can use:

qutebrowser --qt-arg name qutebrowser-profilename

This works in the published release.

To set a custom app_id under Wayland is now possible in the Git version of qutebrowser. It hasn't been released yet but has been merged:

qutebrowser --desktop-filename-name qutebrowser-profilename

Related issue is: qutebrowser/qutebrowser#5245

It should be safe to combine both --qt-arg and --desktop-file-name.

This issue is related to #17, which discusses generating custom .desktop files for profiles. It would be natural for these custom .desktop files to set unique WM_CLASS or app_id that matched their .desktop file name.

e.g. qpm new, qpm clone {profile-name}

E.g. if I want a per-project profile, it's easier to do qpm launch ./profile than qpm -P . launch profile.

What if instead of the complicated config, there was just a shell script like:

ln -s {{ xdg-config-qb }}/qutebrowser.conf {{ dest-config-qb }}/qutebrowser.conf
mkdir -p {{ dest-config-qb }}/conf.d
cp {{ xdg-config-qb }}/conf.d/* {{ dest-config-qb }}/conf.d/

Icons can be used with .desktop files and in at least rofi and fuzzel 1.8.0+. We can fetch the profile home page's favicon and save it to the profile dir, and default to qutebrowser's icon if there's none present. Icons can be customized just by replacing the file.

Basically elevate a session to a profile. qute-ssb -p music could be the whole invocation to create a new profile based on sessions/music.yml.

Does the glob match symlinked dirs? Should it? What about their contents?

https://git.sr.ht/~adnano/wmenu is the new default menu in sway.

• #31
• #32
• #30
• #24 (via click)
• adopt pyproject.toml (#33)
• reevaluate xdg paths: we sometimes use qbpm and sometimes qutebrowser-profiles
• allow paths other than the default qutebrowser config dir as the root config
• choose: add primary profile to menu?
• configurable menu prompt
• nice to have: config file (toml)
• probably more tests
• switch from master to main
• provide portable release with installation instructions
  • github release (source code, wheel?, egg? zipapp?)
  • pypi
• release announcement for qb mailing list
  • ask someone to post it on r/qutebrowser
  • stretch goal: blog post
• update readme
  • promote choose
  • use cases
  • screenshot with icons