| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Upstream is deprecating `stdenv.lib`, so let’s do the same.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 7b8164be35c9d82d6e7389a407150a9128f7fb0c.
From the upstream changelog:
> This is an important bugfix release that should resolve several
> outstanding issues and concerns. Since 1.10.0 was released was engaged
> in a lot of discussions and realized that compatibility is more
> important than we first thought. So we're rolling back some breaking
> changes and revise some parts of our roadmap. We will strive to remain
> compatible with other password store implementations - but remember
> this is a goal, not a promise. This means we'll continue using
> compatible secrets formats as well as GPG and Git.
As mentioned in the original commit, I'm still not entirely convinced
that my use case has a future with gopass, their decision to roll back
some of the breaking changes at least makes it possible for me to
upgrade to the latest upstream version without the fear of being locked
in into some gopass-specific format.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
One thing that has annoyed me since quite a while but ultimately didn't
fix yet, was that the urgency hint was only set for one millisecond.
I don't know how this would look like in a desktop environment, but in
my environment the corresponding workspace only flashes red and then
turns back to blue (the default color) whenever I get a new message.
Since I do not constantly switch to Psi to check whether there is
something new, I sometimes responded very late to messages even though I
didn't want to (eg. not actively working on something).
Of course, I also don't want to be interrupted when I'm actually in
zone, but luckily the way urgency hints are displayed in my environment
is pretty unobtrusive and there is no flashing, blinking or even sounds.
So the only difference is that I do not need to switch to Psi anymore,
to check whether there are new messages.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a common pattern I encounter on a daily basis, which involves
copy & pasting the store path of a failed build to "nix log".
Now the same is just a matter of running "nlast" and we get rid of the
useless copy & paste.
The way we do this does have a small goof: Using mtime (or really any
time, other than atime, which commonly is disabled) is not going to work
if we *repeat* an older Nix build, since this will only change the log
file but the prefix directory will be unchanged.
Since addressing this goof would most likely result in iterating through
*all* log files, I'm not doing it since I think it doesn't occur very
often in practice. If I happen to be wrong on that, we could still go
for the heavyweight solution.
Also, I went for implementing this in Python instead of a shell script,
because the latter would not only be less readable but also way slower
since we need to either fork out for every stat command or use ls and
head to figure out the newest file.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
No particular reason, other than current Psi version "feeling" too old
and I'm feeling somewhat adventurous.
The usrsctp library is now needed for Jingle, so I added a small build
of it directly from master as well. Who wants old release versions,
right?
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
Added this when contributing to a GDScript project and since I know a
few persons who implement their games using Godot, I might need to write
GDScript at some point in the future again, so the syntax highlighting
plugin comes in handy.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is actually needed to build the axbo program, which I have rarely
used during the past years. However, I'm not absolutely sure that I
won't be using this again so I decided to fix it, since all that needed
to be done is take an additional patch from Debian that fixes
compatibility with newer JDK versions.
Since the patch changes configure.in and Makefile.am, we need to
regenerate all the files for autotools as well and since there were old
m4 files laying around I deleted them in preAutoreconf.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Version 1.10.X switches the default to new MIME-based format which
breaks interoperability with pass and other implementations.
I'd gladly switch to that format, but the 1.10.0 changelog also
announces plans to remove support for GnuPG and Git in the long term:
> The goal is to remove the support for multiple backends and any
> external dependencies, including git and gpg binaries.
GnuPG and Git support is the reason why I started using pass and
ultimately switched to gopass. If the latter stops being a viable
password manager, switching back to pass will be much harder with the
new MIME format.
There is also an upstream issue[1] about this and while I haven't read
through *all* the comments, other people seem to have similar reasons
for switching to gopass.
So far however I'm not convinced that my use case will have a future
with gopass, so I'll stay at 1.9.x until I've had the time to properly
research other options or maybe even stay with gopass (and go all-in
with the new MIME format).
[1]: https://github.com/gopasspw/gopass/issues/1365
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
For translations there is a nice web interface called Pontoon[1], which
should it make conventient to edit translations.
However, for developers like me I'd call this quite inconvenient, so I
need a Vim plugin to make it at least more pleasing to look at :-)
[1]: https://github.com/mozilla/pontoon
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
While being at it, let's bump the Nix syntax/indentation plugin to the
latest version, since there are a few quirks that were annoying me since
quite a while but I was too lazy to actually fix.
I haven't checked whether the latest version fixes these quirks since I
don't know them on top of my head, but if it doesn't I surely will
stumble on them soon enough.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
So far I had termencoding set to "ascii", because my terminal was only
really able to display ASCII characters and nothing else.
Since this is no longer the case, we can also get rid of this
restriction in my Vim configuration.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been using this configuration since years already but so far it has
been residing in ~/.muttrc and I copied to new machines accordingly.
The reason why I didn't add it here was because the config was too ugly
and I never got so far as to properly re-do it.
Unfortunately, the config is still ugly as hell, but at least we now
generate it from a structured Nix format and also the IMAP/SMTP user and
server infos are now retrieved via gopass instead.
This also includes my small prank multipart/alternative filter, which
should hopefully "encourange" recipients to disable HTML
parsing/rendering.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
With the switch to a proper Unicode capable font, we no longer need to
patch gopass and simply can now enjoy a proper tree view and also one
less patch to maintain.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I really don't have a lot of other things to blame for forgetting this
in the first place, but let's just assume that the temperatures here
right now are higher than I'm used[TM] to and thus my brain wasn't
working.
On the other hand while writing this I also took a peek and aparently
it's around 20 degree celsius right now, which would be... well...
... okay, I just forgot about that and I feel ashamed now. Go on!
Nothing to read here!
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The latest master version no longer crashes on Jingle file transfer
requests. So alongside updating to the latest Git version, I also
dropped the patch disabling Jingle.
Another reason for updating is simply because the client version already
feels old (heck, it's been February since the last update) and I'm
really craving for fresh new bugs.
I rebased the patch for the default configuration against current master
with no changes in configuration (only obsolete stuff removed) and fixed
the move of the src/plugins directory to the project's root directory.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The patch I added to xournal was for keeping the aspect ratio when
annotating PDFs with images. However, looking at xournal++ the aspect
ratio is kept by default when resizing via corners so the patch is not
needed.
Since I don't really care a lot whether it's xournal or xournal++ and as
long as it does the very little things I intend to use it for, I don't
mind if it has too many features for my taste.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
The import list of list.go has changed upstream, so the rebase of this
patch doesn't change anything in its functionality but just makes sure
that it applies against gopass version 1.9.0.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is quite useful in CSS files and others to directly highlight the
colours in the actual colour value rather than with the generic colour
of the syntax file.
To make sure we don't break the after/syntax files for Haskell and HTML,
I also changed the way we install those files in the output directory so
that if a file already exists, it is appended to rather than
overwritten.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
We essentially only want to have the ftdetect and syntax files,
everything else is just cruft that is not in any way related to Vim.
Ideally we want to do a whitelist approach instead of the "remove
everything unneeded" we're doing right now, but since I don't want to
refactor the whole Vim expression I'll leave it the dirty[TM] way.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When getting an incoming file transfer, Psi has crashed a while ago and
I unfortunately don't remember the exact details. However, since those
stanzas are going to be re-delivered every time we start Psi again, I'd
like to debug this in an isolated environment rather than being more or
less forced to stay unavailable (especially annoying if someone is
trying to send a file and then you stay offline for hours).
So until I get to debugging this and ideally also test this in an
automated fashion, I'll disable it for now since I'm not using Jingle
sessions at the moment.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
Updating to latest master fixes one of the most annoying theming issue
where the chat message input box text will turn black on dark background
for my custom Qt theme.
There are also quite a lot of fixes in master (which is still
unreleased), which we want to have as well.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
This probably needs a bit of refinement when it comes to indentation,
but at least we get proper syntax highlighting, which is the main point
here.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
The upstream service was shut down at September 11th 2019, so there
really is no need anymore for this package.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Qt applications are no longer implicitly wrapped since a while[1] and so
we new have to use wrapQtAppsHook instead, which also makes the wrapping
for Psi obsolete.
To make sure we don't run into startup errors again, I added a small VM
test, which checks whether the application starts up properly.
[1]: https://github.com/NixOS/nixpkgs/commit/f79fd2e826dd95b3b64839d3e0bec8ae1dfab17e
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
The current master version contains a number of fixes, one of them I
encountered by myself, which is a crash when changing profile settings.
I've updated the configuration patch accordingly, because a few
(obsolete) settings got removed upstream.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
Both strace and xt are trace log formats, so imposing my own distaste
for overly long line length won't make a difference, as they won't
change their "coding style" ;-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
Unfortunately these days I have to debug a lot of PHP code, so having
syntax highlighting (even though the syntax file is pretty terse) and
being able to fold Xdebug traces is quite useful to have.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is from the current 2.0 development version and has most of my own
configuration preferences built-in.
Right now, the theming is pretty much a work in progress and the chat
input currently shows black text on dark grey background, which is quite
a nuisance to use.
Another thing that's currently not working (or just for a very short
amount of time) are window manager urgency hints.
Nevertheless however, I'm already using it as my main XMPP client
despite these issues.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
Jinja2 seems to be quite popular these days for all sorts of templates,
so let's actually use the syntax file from the actual Jinja2 package.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Unfortunately, I need to deal with PHP code occasionally, so let's make
syntax highlighting less painful.
I'm not sure why the option is called PHP_vintage_case_default_indent,
but I prefer case statements to be indented.
Apart from HTML/SQL syntax highlighting within PHP strings, I also want
to prevent short open tags, so that whenever I stumble on code using it
I can immediately fix them.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
The pcsclite derivation results in multiple outputs, so let's make sure
we actually get the right path to the library instead of ending up using
that from the "bin" output (which obviously doesn't exist).
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
Constantly getting errors on type hints and "unknown" print() arguments
is very annoying, especially because I almost exclusively use Python 3
nowadays.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
The upstream project already provides a Vim plugin so we only need to
reference that using the existing meson.src attribute.
However, I needed to patch out a very annoying thing, which would echom
every time the indentexpr is called. Most likely this was left in for
debugging.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
This includes a revert of the recent indentation changes which introduce
more problems than they actually solve.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This basically switches the source to my pull request with a few fixes
for indentation:
https://github.com/LnL7/vim-nix/pull/19
The main annoyance was that writing "with ...;\n\nlet" was indented one
level deeper and I'm regularly writing small Nix expressions with
something like this, eg. to quickly test things or abuse the Nix sandbox
for programs I don't want to run unsandboxed ;-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
This is used by Habitica and for maintaining my fork I sometimes[TM]
unfortunately have to edit .vue files.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is mainly to catch up with the syntax highlighting fixes that were
done in the respective plugins.
The setlocals in ftplugin/nix.vim from LnL7's plugin are now gone and
it's one setlocal with line continuation, so I had to turn the simple
grep into a small sed script.
Another thing I added while at it is to add the single quote to
iskeyword, because it can be part of a Nix identifier. I did that by
replacing the dash, because the latter now is part of the setlocal of
the aforementioned ftplugin.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
The patches are basically the same but only the files were moved to a
different place in the upstream repository.
Tested building and execution.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
I've introduced this in 45aab49b33ab2cd4c327b996d6924f104b038193.
It turns out that autocomplete_and_align when leaving insert mode is
more annoying than useful, because first of all I use hledger and it's
syntax additions and second I also use different currencies, which then
get aligned and autocompleted into "something with EUR".
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
I only want gopass to use ASCII symbols. This is something I already
hated in pass, but I never changed it. By switching to gopass now, it's
a great opportunity to change it.
Second, I use "less -R" as a pager, which supports color so there really
is no need to disable colors before piping it to my pager.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
The build for i686-linux has been failing for a while and the program is
actually only used on x86_64-linux machines, plus I'm not maintaining it
anymore.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
My main hledger file already contains a lot of entries even though I
just started using hledger, so folding all of that crap away seems to be
a good idea.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This has annoyed me for a while now, especially when writing Haskell
code.
Let's say if I have something like this:
foo :: Num a => a -> a
foo a =
b
where
b = a + 1
Sleuth will detect that the indentation level is 2 spaces, but in
reality what I want is to have it at 4 spaces. So turning off Sleuth
will solve that problem, especially because we can still invoke it
manually.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
The plugin really is for Ledger instead of hledger, but both should be
compatible with the syntax. If we use something that's not compatible we
can still patch it in.
I also set the default currency to Euro and added an auto-align after
leaving insert mode because I'm lazy ;-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The config.patch doesn't apply for Gajim 1.0 anymore anyway, so let's
throw everything away, including my custom config in order to start with
a new abomination.
With the new approach, I'm going to patch the configuration defaults
*directly* into Gajim, because one of the problems with the old approach
was that whenever specifics about a configuration value has changed, I
didn't get noticed by a patch failure.
So in the end the config I was ending up was a big mess.
I'm going to start this with a new unpatched version and someday get to
a patched version that I'm staisfied with... hopefully ;-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The actual executable is libexec/travic-sign/travic-sign and not
libexec/travic-sign, so let's actually fix this in the native messaging
host config file.
This is mainly for the sake of OCD, because I'm not using Chromium
anymore and manually insert the path (I know, someday[TM] I will
automate this).
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
The features that we needed back then are now already in stable, so no
need to use staging anymore.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
This one is an old leftover from where I ran patched versions of NixOps,
but nowadays it is already in <nixpkgs>, so no need to keep it around.
Other than that, with Hydra now running in restricted eval mode it will
run into an eval error.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
A lot has changed since the version I had in here and the current
upstream master, so let's get all the new bugs and features :-)
Here is a comparison with all the commits that have happened since then:
https://github.com/NixOS/nixops/compare/d1907cb1a4defa...eb6d25688a35de
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The wine-no-unixfs.patch doesn't apply anymore, so we need to get a
newer version of the patch now from http://achurch.org/patch-pile/,
which is a bit different in that it adds --disable-unixfs as a flag to
configure. We don't have autoreconfHook in nativeBuildInputs, so that
flag will simply be ignored but unixfs will be disabled regardless
because the flag in config.h.in is ENABLE_UNIXFS and it's not defined by
default. The reason why I still added it to configureFlags is to prevent
enabling it by accident if autoreconfHook should be part of the wine
derivation in upstream <nixpkgs>.
In addition to that I've made disabling getuid a bit more clear and with
a comment about why we need to disable it.
Signed-off-by: aszlig <aszlig@nix.build>
|