| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Haxe plugin(s) I've used so far (vim-haxe and vim-haxe-syntax) are
no longer actively maintained since 2014.
On the other hand "vaxe" is based on the work on vim-haxe and
vim-haxe-syntax, is actively maintained and supports newer language
features of Haxe as well.
I've patched out syntax highlighting for ',' and ';', because I really
get eye cancer with this and reminds me a bit about the annoying bold
colons when using nickname completion back in the days where BitchX
users were widely seen on IRC.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
| |
The reason is that for terminals that have a width of 80 characters,
having a line with exactly 80 characters will wrap it.
I've wrapped most of my code in 79 characters since a while manually, so
it's time to enforce this by the editor.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
The default is 50, which is a bit small for my taste.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
This one is annoying because it enables mouse mode and it's sourced
*after* our defined configuration. Setting skip_defaults_vim disables
this behaviour.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
I don't use anything that's machine specific within my Vim
configuration (and even if, we can pass it via the callPackage
arguments) so it's kinda pointless that it's a module instead of a plain
package (override).
This makes it also easier to nix-build the package without the need to
go through the module system.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
IMHO it makes more sense to use the latest rc kernel instead of the
latest stable kernel to run this test, because what we're actually
testing here is whether our bfq-by-default.patch is working.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
This has been removed upstream and is no longer needed, see commit
torvalds/linux@5c279bd9e40624f4ab6e688671026d6005b066fa.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This dissolves the user.aszlig.system.kernel module, which was not only
to stay on the latest bleeding edge kernel but also to enable BFQ. The
latter has been factored out already a while ago already.
Originally, I had a fully custom kernel config for mmrnmhrm and dnyarri,
but it's no longer the case and thus the user.aszlig.system.kernel
module is now no longer needed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Additions and changes:
* Reduce cost of player station parts
* Show some system information on hovering over stars in the navigation
interface
* Show system name on the system screen in the navigation interface
* Properly beam away a player's mech when a player beams off the world
* Deploying to asteroid fields puts you in a position related to where
in the field your ship is
* Allow any number of script panes with no source entity
* Add player.interact lua binding
* Keep player from starving when in a mech
Bug fixes:
* Various NPC and Monster behavior fixes
* Fix issue where player ships from other systems would be visible on
the navigation screen
* Fix issue where deploying to a party member could result in deploying
a mech to their ship
* Improve jarring movement of the sky during flying and warping
* Fix issue where inventory items would count twice in crafting
interfaces
* Fix parameters argument for spawnnpc console command
* Fix issue allowing the player to fly the ship before fully repairing
it
The full upstream release announcement can be found at:
http://playstarbound.com/starbound-1-3-2-changelog/
Tested using the games.starbound VM test.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
| |
|
|
|
|
| |
cc @aszlig
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The upstream issue is systemd/systemd#3879 and this bug has annoyed me
for a while now. I've also opened a pull request (NixOS/systemd#12) to
the NixOS fork of systemd, but this is pending since almost a month now
and the bug is still annoying as fuck, so let's patch it in vuizvui.
I'm not yet porting this to other machines yet, because I want to test
whether this actually really solves my problem (even though it's exactly
what the upstream bug describes) or whether we need to patch something
else as well.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell (uses networkd as well)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are two other occasions where packageOverrides are still in use,
one of them is @sternenseemann's fliewatuet machine and another one is
@devhell's package profile.
I've replaced every other occurence of packageOverrides and replaced it
with overlays and checked the store path hash after evaluation.
The reason why I left @sternenseemann's fliewatuet alone was that for
I wasn't quite sure whether "bluez = pkgs.bluez5" is still needed or
intentional to pin it to version 5. Because if it's not the case the
packageOverrides can just be dropped because bluez is already bluez5 in
upstream <nixpkgs>.
For @devhell's package profile, I did the conversion, but the store path
turned out to be a different one than what it was prior to the change.
I did take a quick look at the requisites of the drv and found that sox
was one of the different paths that led to the change in the final store
path.
This obviously needs to be tested and/or investigated first.
Other than that, the main reason why I'm moving everything to overlays
is that it's the replacement for packageOverrides and also has a better
way to pass through chains of overrides than packageOverrides had.
My guess is that after NixOS 17.09, the old packageOverrides function
will be removed, so let's make sure we're ready for that.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell, @sternenseemann
|
|
|
|
| |
Let's see what the fuss is all about.
|
| |
|
|
|
|
| |
When the connection drops packages, it should be picked up by the script.
|
|
|
|
| |
Based on comments in https://github.com/openlab-aux/orgafoo/issues/257.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
sane has a file called `net.conf` which is a list of hosts that are searched for
remote scanners.
|
| |
|
|
|
|
|
|
| |
Add an option to specify the file where new data should be appended to.
Check the size of the actual downloaded file.
Add IPv6 and IPv6 checks and a version field for outputs.
|
|
|
|
|
| |
Apparently `enableACME` doesn’t generate certificates for the right subdomains
if they are on the same machine in different virtual hosts.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Until now, the config on the actual server was deviating because I changed it
locally.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Now that the scheduler is in mainline, I think there is nothing now to
stop us from unleashing it to end users :-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
| |
The service and test has been broken for a long time now and nobody
really has any interest in using it or even fixing it, so I'm removing
it to decrease the amount of crap we have in there.
If somebody still wants to use this someday we can still bring it back.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
Not everybody likes to have the latest release canidate kernel, so we
now have an option called vuizvui.system.kernel.bfq.enable, which *only*
enables the BFQ scheduler per default.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I previously wrote that patch in a hurry, so I thought it would be
enough to set CONFIG_DEFAULT_IOSCHED to "bfq". But in block/elevator.c
the actual default for blk-mq is a constant and can't be configured via
CONFIG_DEFAULT_IOSCHED.
So we're now patching just that constant and nothing more.
Also, I've enabled CONFIG_DM_MQ_DEFAULT, because the DM devices need to
be switched to blk-mq as well and for example on dnyarri I'm actually
using the device mapper for LUKS.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
| |
A simple script to gather DNS & download speed data.
|
|
|
|
|
|
|
| |
We no longer need to use linux_testing, because kernel 4.12 is stable
since yesterday.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
I need to thoroughly test the latest development version, so it's a must
to keep it up to date.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Signed-off-by: devhell <devhell@mailfresser.de>
|
|
|
|
|
|
|
| |
For whatever reason the /boot configuration was missing and subsequently
nixos-rebuild would fail. Thanks for pointing out the error @aszlig!
Signed-off-by: devhell <devhell@mailfresser.de>
|
|
|
|
|
|
|
| |
Let's see how the touchpad on this new laptop behaves with libinput
instead of synaptics.
Signed-off-by: devhell <devhell@mailfresser.de>
|
|
|
|
|
|
|
| |
I no longer need to actively debug the kernel or do much development on
the machine, so this is no longer needed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
This reverts commit 2e90b9562939208e5392790834c6ffd89aede692.
Sorry about this. I was wrong as it seems networking.wireless is
required for connman.
|
|
|
|
| |
Not even sure if it is needed anymore to keep connman working.
|
| |
|