Package Details: roxterm 3.7.3-1

Git Clone URL: https://aur.archlinux.org/roxterm.git (read-only)
Package Base: roxterm
Description: Tabbed, VTE-based terminal emulator
Upstream URL: https://github.com/realh/roxterm
Licenses: GPL3
Submitter: Barthalion
Maintainer: hrauch (SolarAquarion)
Last Packager: SolarAquarion
Votes: 8
Popularity: 1.112084
First Submitted: 2018-01-07 16:41
Last Updated: 2018-10-06 18:32

Latest Comments

1 2 Next › Last »

zaibon commented on 2018-09-28 15:21

Seems the 3.6.1 version has a bug that has been already fixed in 3.7.2

link to the bug: https://sourceforge.net/p/roxterm/bugs/116/

I can have a look at this package to upgrade to 3.7.2 if needed, just let me know

rusty commented on 2018-03-03 21:17

@SolarAquarion I hope it stays that way, thank you so much for doing great work.

SolarAquarion commented on 2018-03-02 19:55

@rusty the realh fork is great

rusty commented on 2018-03-02 18:56

yes, man you made it !!! :) Now roxterm window opens in a normal size, Thank You !!!

SolarAquarion commented on 2018-03-02 13:25

I have updated the package to the 3.5 series

hrauch commented on 2018-03-02 10:00

@SolarAquarion No prob. Consider it done :-)

SolarAquarion commented on 2018-03-01 18:31

https://github.com/realh/roxterm/releases/tag/3.5.1

@hrauch can you add me as a maintainer?

hrauch commented on 2018-02-26 15:47

@SolarAquarion thanks for the hint about the fork. Didn't know about it.

SolarAquarion commented on 2018-02-26 13:42

https://github.com/realh/roxterm/releases/tag/3.5.0

there has been a fork with lots of improvements

hrauch commented on 2018-01-31 22:55

@rusty: sorry, can't reproduce that on my box (I'm running Manjaro (which is based on Arch) with XFCE on a HiDPI screen (resolution: 3840x2160). OK, roxterm does come up kind of small, but not in 20x4 (which would be invisible).

Furthermore, I also tried the --geometry option. It works for me. (I tried 1024x768, 800x600, etc.)

Concerning the key thing:

I found a hint in the makepkg page in the Archlinux Wiki:

https://wiki.archlinux.org/index.php/Makepkg#Signature_checking

and the linked blog post:

http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/

=> So, this is documented, but I wasn't aware of it either, at least not initially.

Conclusion: Only keys used for pkg sigs in the core, extra, community repos are automatically managed by pacman. The remaining ones (for AUR pkged stuff) are supposed to be managed by the user, meaning that the user has to fetch the corresponding pubkey(s) by himself, because they go into the user's keyring.