Jørgen Lien Sellæg
Jørgen Lien Sellæg
This was introduced upstream somewhere in this diff https://github.com/webpack/watchpack/compare/v1.6.1...v1.7.2
I encountered the same bug and manually selected version 1.6.1 in my `package-lock.json` file and was able to move on with my day. Here is the entry for watchpack 1.6.1....
I think I've run into the same problem. When running 3.13 I get a `/etc/resolv.conf` containing the correct nameserver. In 3.14 it contians `nameserver 127.0.0.11` for some reason.
@kevzettler I managed to use this package through npm by manually adding: > package.json > > ``` json > "bootstrap-sortable": "git://github.com/drvic10k/bootstrap-sortable.git#3228ddab69ee6af8808d6be377e532ef0da5a563" > ``` Where 3228ddab69ee6af8808d6be377e532ef0da5a563 corresponds to version 1.12
I'll got some motivation figuring this out, I really miss emacs navigation. I'll reopen and report.
I think we might need to supply the config by calling something like get_default in gtk. I'm investigating now.
It's possible to just start using emacs configuration. In `/usr/share/themes/Emacs/gtk-3.0/gtk-keys.css` you can find definitions for emacs. For vim checkout the one @eidheim linked. Include this css file into gtk-init-file or...
@eidheim We might want to change our signal names in config.json to correspond with gtk-signals so that configs like this works out of the box, even on search, save, etc....
Hi, @eidheim! I have also encountered this use case. I would suggest that we add the subdirectory name to open files with the same name: ```js // as it is...
I'll try to implement this tonight.