mailchuck / PyBitmessage

This repository has been discontinued, please use the official PyBitmessage repository

Home Page:https://github.com/Bitmessage/PyBitmessage

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

UI settings in portable mode on Unix

PeterSurda opened this issue · comments

Came over BM. Basically, the UI settings, which on Win are stored in the registry, are in a file on Unix and this does not take into account the portable mode.

---cut---

Of course the old file will exist until you delete it. But setting XDG_CONFIG_HOME does work.


that file still does do exist, mate.

just telling you. No offense, mate.


I don't know what

~/ .config/PyBitmessage/ py bitmessage qt .conf

is, but if you are talking about ~/.config/PyBitmessage/pybitmessageqt.conf file then that's not a PyBitmessage configuration file.
The configuration file is called keys.dat, the database file is called messages.dat and the logfile is debug.log. If these three files are in the correct location then there is no bug.

The pybitmessageqt.conf file is a qt thing, it stores the settings of the PyBM window size and whatever you can resize or move (with)in it. You may try to set the XDG_CONFIG_HOME env variable. Try running it like this:

XDG_CONFIG_HOME=/some/portable/path/ python bitmessagemain.py

and check whether the pybitmessageqt.conf gets created there.


I also report I used today's 0.5.7 Master PyBM

Did I miss anything?

~/ .config/PyBitmessage/ py bitmessage qt .conf

is being created in portable mode in the wrong place (directory).

It should not be created there, in that dir (the NON-portable DIR)

In portable mode it must be in the /src/ subdirectory from where bitmessageMain.py was launched

so this .conf file is in the wrong directory

I hope, I maybe cleared it up. Thank you, Gentlemen.


What exactly is your problem? Your OP is unreadable.


Sorry, actually I have to take that back. But as I said, it is a low priority bug.

the .conf file still shows up even though portable mode is active. But it has seemingly little purpose anyhow.


I noticed the bug is gone now.

Well done, Peter.


I run today's BM 0.5.7 master.

Noticed 2 things:
#1 intel HD notebook graphics seem to be supported (OpenCL) now for hashing, the earlier error message is gone. Very nice! :-)
#2 In portable mode, a file " ~/ .config/PyBitmessage/ py bitmessage qt .conf " keeps being generated in that "non-portable" dir.,

but it should belong in .../src/ where one launched the bm-main.py executable.
but this is a rather minor imperfection.

BM soon will outlaw e-mail forever!