Jonas Møller
Jonas Møller
@SergioBenitez Sounds like a good idea to just do both, I'll submit a PR.
@nobbele Tested this on an Ivy Bridge Intel HD 4000 machine, on my end it's not to do with the limits, it simply isn't finding any adapters at all on...
It seems like this is all resting on a good ol' pile of horrifying hacks: https://github.com/company-mode/company-mode/issues/409#issuecomment-434820576 @hlissner Should doom include workarounds for this or just wait for upstream (note: the...
From the `pcomplete` source: ```emacs-lisp ;; FIXME: it only completes the text before point, whereas the ;; standard UI may also consider text after point. ;; FIXME: the `pcomplete' UI...
Pinging @hlissner The following patch has worked for me: ```emacs-lisp ;;; eshell-company-patch.el -*- lexical-binding: t; -*- ;; Copyright (C) 1999-2020 Free Software Foundation, Inc. ;; Author: John Wiegley ;; This...
@hlissner Here's a diff: ```diff diff -u /tmp/em-cmpl-eshell-complete-parse-arguments.orig.el /tmp/my-eshell-complete-parse-arguments.new.el --- /tmp/em-cmpl-eshell-complete-parse-arguments.orig.el 2020-08-28 13:05:18.185416575 +0200 +++ /tmp/my-eshell-complete-parse-arguments.new.el 2020-08-28 13:05:57.378570724 +0200 @@ -1,71 +1,64 @@ (defun eshell-complete-parse-arguments () "Parse the command line...
@nobbele I know, but `from_pixels` takes raw pixel data, and is [what `from_path` does internally](https://docs.rs/ggez/0.8.0-rc0/src/ggez/graphics/image.rs.html#125-151), which was my suggested workaround. The `Image::from_bytes` function accepts encoded image data, e.g raw `.png`...
I currently just export this from a `ggez_compat` file to port my code: ```rust pub trait FromBytes: Sized { fn from_bytes(ctx: &mut Context, encoded: &[u8]) -> Result { Self::from_bytes_srgb(ctx, encoded,...
@PSteinhaus My specific use-case for this was embedding `.png` images with `include_bytes!(...)` for quick mockups (makes it easier to just send someone an executable and have it work.) I guess...
@PSteinhaus Thanks, was able to port all my code to `0.8.0-rc0`! The last hickup was that the `AsStd140` proc-macro expects `crevice` to be available globally, and because `AsStd140` is used...