Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

thunar configuration #161

Closed
wants to merge 1 commit into from
Closed

thunar configuration #161

wants to merge 1 commit into from

Conversation

adrelanos
Copy link
Member

Changes date style to iso format.
Disable network bookmark by default.
Disable thunar-volman by default.

Changes date style to iso format.
Disable network bookmark by default.
Disable thunar-volman by default.
@adrelanos
Copy link
Member Author

Real solution would be QubesOS/qubes-issues#1885 though which encompasses a lot more.

@codecov-io
Copy link

Codecov Report

Merging #161 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #161   +/-   ##
=======================================
  Coverage   65.48%   65.48%           
=======================================
  Files           2        2           
  Lines         394      394           
=======================================
  Hits          258      258           
  Misses        136      136

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 152cec3...6c61888. Read the comment docs.

@fepitre
Copy link
Member

fepitre commented Aug 14, 2019

@adrelanos: yes maybe we could implement it directly? Initially, I put a really straightforward configuration but hardened one is much better.

@adrelanos
Copy link
Member Author

I am not working on this one anymore. Since QubesOS/qubes-issues#1885 made progress, is the way to go, and this one would be conflicting with it, I am closing this one.

Feel free to come up with pull requests of your own, though. (Not an administrative statement. Just me stating I am not working on this specific solution anymore.)

@adrelanos adrelanos closed this Aug 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants