saundersp/saundersp-overlay
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Formatting spaces to tabs

Browse Source
This commit is contained in:
saundersp
2025-02-12 16:36:09 +01:00
parent 9add3bce03
commit f86901cf88
3 changed files with 52 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files

48
app-containers/lazydocker/metadata.xml
View File

@@ -1,28 +1,28 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd"> <!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata> <pkgmetadata>
<maintainer type="person"> <maintainer type="person">
<email>torokhov-s-a@yandex.ru</email> <email>torokhov-s-a@yandex.ru</email>
<name>Sergey Torokhov</name> <name>Sergey Torokhov</name>
</maintainer> </maintainer>
<longdescription lang="en"> <longdescription lang="en">
A simple terminal UI for both docker and docker-compose, written in Go with the gocui library. A simple terminal UI for both docker and docker-compose, written in Go with the gocui library.
Minor rant incoming: Something's not working? Maybe a service is down. docker-compose ps. Minor rant incoming: Something's not working? Maybe a service is down. docker-compose ps.
Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart. Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart.
Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps. Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps.
Right so the service must have just stopped immediately after starting. Right so the service must have just stopped immediately after starting.
I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services. I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services.
I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service. I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service.
I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again, I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again,
but now I've got one service hogging a terminal window even after I no longer care about its logs. but now I've got one service hogging a terminal window even after I no longer care about its logs.
I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason. I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason.
Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service. Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.
What a headache! Memorising docker commands is hard. Memorising aliases is slightly less hard. What a headache! Memorising docker commands is hard. Memorising aliases is slightly less hard.
Keeping track of your containers across multiple terminal windows is near impossible. Keeping track of your containers across multiple terminal windows is near impossible.
What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well). What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well).
Lazydocker's goal is to make that dream a reality. Lazydocker's goal is to make that dream a reality.
</longdescription> </longdescription>
<upstream> <upstream>
<remote-id type="github">jesseduffield/lazydocker</remote-id> <remote-id type="github">jesseduffield/lazydocker</remote-id>
</upstream> </upstream>
</pkgmetadata> </pkgmetadata>

8
app-text/calibre/calibre-7.24.0.ebuild
View File

@@ -215,10 +215,10 @@ src_test() {
src_install() { src_install() {
# Bug #352625 - Some LANGUAGE values can trigger the following ValueError: # Bug #352625 - Some LANGUAGE values can trigger the following ValueError:
# File '/usr/lib/python2.6/locale.py', line 486, in getdefaultlocale # File '/usr/lib/python2.6/locale.py', line 486, in getdefaultlocale
# return _parse_localename(localename) # return _parse_localename(localename)
# File '/usr/lib/python2.6/locale.py', line 418, in _parse_localename # File '/usr/lib/python2.6/locale.py', line 418, in _parse_localename
# raise ValueError, 'unknown locale: %s' % localename # raise ValueError, 'unknown locale: %s' % localename
#ValueError: unknown locale: 46 #ValueError: unknown locale: 46
export -n LANG LANGUAGE ${!LC_*} export -n LANG LANGUAGE ${!LC_*}
export LC_ALL=C.utf8 # bug #709682 export LC_ALL=C.utf8 # bug #709682

48
dev-vcs/lazygit/metadata.xml
View File

@@ -1,28 +1,28 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd"> <!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata> <pkgmetadata>
<maintainer type="person"> <maintainer type="person">
<email>torokhov-s-a@yandex.ru</email> <email>torokhov-s-a@yandex.ru</email>
<name>Sergey Torokhov</name> <name>Sergey Torokhov</name>
</maintainer> </maintainer>
<longdescription lang="en"> <longdescription lang="en">
A simple terminal UI for both docker and docker-compose, written in Go with the gocui library. A simple terminal UI for both docker and docker-compose, written in Go with the gocui library.
Minor rant incoming: Something's not working? Maybe a service is down. docker-compose ps. Minor rant incoming: Something's not working? Maybe a service is down. docker-compose ps.
Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart. Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart.
Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps. Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps.
Right so the service must have just stopped immediately after starting. Right so the service must have just stopped immediately after starting.
I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services. I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services.
I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service. I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service.
I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again, I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again,
but now I've got one service hogging a terminal window even after I no longer care about its logs. but now I've got one service hogging a terminal window even after I no longer care about its logs.
I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason. I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason.
Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service. Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.
What a headache! Memorising docker commands is hard. Memorising aliases is slightly less hard. What a headache! Memorising docker commands is hard. Memorising aliases is slightly less hard.
Keeping track of your containers across multiple terminal windows is near impossible. Keeping track of your containers across multiple terminal windows is near impossible.
What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well). What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well).
Lazydocker's goal is to make that dream a reality. Lazydocker's goal is to make that dream a reality.
</longdescription> </longdescription>
<upstream> <upstream>
<remote-id type="github">jesseduffield/lazydocker</remote-id> <remote-id type="github">jesseduffield/lazydocker</remote-id>
</upstream> </upstream>
</pkgmetadata> </pkgmetadata>