sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: Scrolling problems on large files when reversing scroll direction. Letters get inserted.
Labels: bug

<!-- Before reporting: search existing issues and check the FAQ. -->

- `nvim --version`: NVIM v0.5.0-3de9452
- `vim -u DEFAULTS` (version: ) behaves differently? Issue does not occur in Vim8 or MacVim.
- Operating system/version: macOS Catalina
- Terminal name/version: iTerm2 3.3.9
- `$TERM`: xterm-256color

### Steps to reproduce using `nvim -u NORC`

1. Open a large typescript file (mine was 5600 lines).
2. syntax on
3. Make sure there is inertial scrolling in macOS. It also happens without inertial scrolling on (but harder to do). Without inertial scrolling, you can scroll really fast and then for some reason inertial scrolling effects turn on (it continues scrolling even if you stop) and causes the problem.
4. Scroll as fast as you can downwards. Once you hit the bottom of the page, immediately scroll as fast as you can upwards. Once you hit the top of the file, keep scrolling up. 
```
nvim -u NORC
# Alternative for shell-related problems:
# env -i TERM=ansi-256color "$(which nvim)"

```

### Actual behaviour
- Letters `B` will get inserted as newlines at the bottom, and `A` gets inserted when you hit the top of the file.
- Also experience some UI skipping when scrolling up.
- If I scroll down and halfway reverse direction and scroll up, it continues scrolling down.

### Expected behaviour

- No letters being inserted if reversing scroll direction.
- No UI skipping
- I should be able to reverse scroll direction instantly

I've been able to reproduce this bug in iTerm2, Kitty, and Alacritty, but it does not seem to happen in the default macOS Terminal.app.

If I turn on all my plugins, and I do the same scroll, the problem is exacerbated. By the time I hit the bottom of the file, it just gets stuck there and I have to kill neovim. After killing I get these escape codes sent to the terminal:
<img width="1538" alt="image" src="https://user-images.githubusercontent.com/109630/80895377-da6a9080-8ca9-11ea-83b1-77aa870e8688.png">
^[[<65;59;12M
Repository: flutter
Issue: [in_app_purchase] Failed pending purchases are not acknowledged (Android)
Labels: platform-android,p: in_app_purchase,package,a: production,P3,team-android,triaged-android

## Steps to Reproduce

1. Load in_app_purchase plugin
2. Make a self declining purchase with a slow test card on Android
3. Restart application
4. Fetch past purchases with InAppPurchaseConnection.queryPastPurchases()

**Expected results:** Failed purchases should either be acknowledged or decoded with PurchaseStatus.failed. 

**Actual results:** Failed purchases are not acknowledged and are marked as PurchaseStatus.pending when fetched with InAppPurchaseConnection.queryPastPurchases(). Neither completePurchase() nor consumePurchase() are able to acknowledge a pending failed purchase once its status is changed to failed on Google Play.
Repository: godot
Issue: Cannot run Godot on virtual X desktop with xvfb-run and lavapipe
Labels: bug,platform:linuxbsd,topic:rendering,confirmed,topic:thirdparty,crash

**Godot version:**
Godot 4.0(Vulkan) - 4.0.dev.custom_build. f5cd33f39
it works fine with Godot 3.2 GLES 2, 3

**OS/device including version:**
Ubuntu 20.04

**Issue description:**

When I try to open master Godot 4.0 branch in virtual X desktop, then I got a crash:

```
WARNING: XOpenIM failed
     at: DisplayServerX11 (platform/linuxbsd/display_server_x11.cpp:3475)
ERROR: Cant find layer: VK_LAYER_KHRONOS_validation
   at: _check_layers (drivers/vulkan/vulkan_context.cpp:158)
ERROR: Cant find layer: VK_LAYER_LUNARG_standard_validation
   at: _check_layers (drivers/vulkan/vulkan_context.cpp:158)
ERROR: Cant find layer: VK_LAYER_GOOGLE_threading
   at: _check_layers (drivers/vulkan/vulkan_context.cpp:158)
ERROR: Condition "err" is true. returned: ERR_CANT_CREATE
   at: _create_physical_device (drivers/vulkan/vulkan_context.cpp:353)
thirdparty/vulkan/loader/loader.h:396:83: runtime error: load of misaligned address 0xbebebebebebebebe for type 'struct VkLayerDispatchTable *', which requires 8 byte alignment
0xbebebebebebebebe: note: pointer points here
<memory cannot be printed>
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] godots() [0x17c49da] (/mnt/Miecz/godot/platform/linuxbsd/crash_handler_linuxbsd.cpp:54)
[2] /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f7a9de14210] (??:0)
[3] godots() [0x64bccf2] (/mnt/Miecz/godot/thirdparty/vulkan/loader/loader.h:396)
[4] godots(vkDestroyFence+0x24) [0x64c91ed] (/mnt/Miecz/godot/thirdparty/vulkan/loader/trampoline.c:1030)
[5] VulkanContext::~VulkanContext() (/mnt/Miecz/godot/drivers/vulkan/vulkan_context.cpp:1596)
[6] VulkanContextX11::~VulkanContextX11() (/mnt/Miecz/godot/platform/linuxbsd/vulkan_context_x11.cpp:56)
[7] void memdelete<VulkanContextX11>(VulkanContextX11*) (/mnt/Miecz/godot/./core/os/memory.h:119)
[8] DisplayServerX11::DisplayServerX11(String const&, DisplayServer::WindowMode, unsigned int, Vector2i const&, Error&) (/mnt/Miecz/godot/platform/linuxbsd/display_server_x11.cpp:3538)
[9] DisplayServerX11::create_func(String const&, DisplayServer::WindowMode, unsigned int, Vector2i const&, Error&) (/mnt/Miecz/godot/platform/linuxbsd/display_server_x11.cpp:3141)
[10] DisplayServer::create(int, String const&, DisplayServer::WindowMode, unsigned int, Vector2i const&, Error&) (/mnt/Miecz/godot/servers/display_server.cpp:563)
[11] Main::setup2(unsigned long) (/mnt/Miecz/godot/main/main.cpp:1261)
[12] Main::setup(char const*, int, char**, bool) (/mnt/Miecz/godot/main/main.cpp:1188)
[13] godots(main+0x22b) [0x17c37a1] (/mnt/Miecz/godot/platform/linuxbsd/godot_linuxbsd.cpp:49)
[14] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f7a9ddf50b3] (??:0)
[15] godots(_start+0x2e) [0x17c34be] (??:?)
```

Fixing this bug will help a lot with testing Godot with CI

**Steps to reproduce:**
```
apt install -y xvfb
xvfb-run godot
```
Repository: go
Issue: x/tools/go/packages: handle import cycles in tests
Labels: NeedsFix,Tools

In its current implementation, the `go list` driver in `go/packages` looks for the error message `import cycle not allowed` and if found appends the error's ImportStack to the error message, resulting in `import cycle not allowed: import stack: [sandbox/foo sandbox/bar sandbox/foo]`. This misses import cycles in tests, which instead use the error message `import cycle not allowed in test`. However, simply checking for this error and appending the import stack is not a viable solution. The message produced would look like this: `import cycle not allowed in test: import stack: [honnef.co/go/tools/unused (test) honnef.co/go/tools/lint honnef.co/go/tools/runner honnef.co/go/tools/unused]` – this is problematic because `gopls` extracts the import stack from the string via some basic string matching and splitting on whitespace. It would ultimately believe that `(test)` is the package we're trying to import.

Unfortunately, go/packages returns a `type Error struct`, and not an interface, so the obvious solution of returning a structured type is not applicable. We could wrap each import path in quotes, but then gopls has a harder time extracting the paths. However, I don't see any other way.

/cc @matloob @stamblerre
Repository: TypeScript
Issue: Import star should work with export type
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

import star export type

## Suggestion

See the code below.

## Use Cases

See the code below.

## Examples

```ts
// a.ts
const a = 1
export type { a } // expected to be used as type only, user case: sharing type rather than value between source code between nodejs and browser

const b = 1
export type { b }

// export other types

// c.ts
import * as c from './a' // to avoid: import { a as a1, b as b1 } from './a'

declare const a: typeof c.a
declare const b: typeof c.b
```

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: pytorch
Issue: Variational Dropout In RNN
Labels: module: rnn,triaged,enhancement

## 🚀 Feature
Original LSTM cell uses dropout that uses different mask at every time step which is ad-Hoc.According this paper we should use same dropout masks at every time step. [Variational RNN](https://arxiv.org/pdf/1512.05287.pdf)


Here is the screenshot what should ideally happen


![Screenshot_2020-05-03 1512 05287 pdf](https://user-images.githubusercontent.com/50786143/80912419-6c31d680-8d5a-11ea-8d57-33b4d5c61838.png)





## Motivation

As said current implementation is wrong and gives unstable results.So it is extremely important for it to use same dropout masks.






cc @zou3519
Repository: rust
Issue: Tracking Issue for const_btree_len
Labels: A-collections,T-libs-api,C-tracking-issue,A-const-eval,disposition-merge,finished-final-comment-period,Libs-Tracked

This tracks stabilization of the `const_btree_len` feature, which allows calling the below in a constant expression:

- `BTree{Map,Set}::{len,is_empty}()` (#78581)

### Previously tracked here, already stable

- `BTree{Map,Set}::new()` (#71839)

### Steps

- [x] Implementation #71839
- [ ] Stabilization PR
Repository: rust
Issue: Lifetime elision makes arg lifetime depend on return value reference
Labels: A-diagnostics,A-lifetimes,A-borrow-checker,T-compiler,D-terse

A friend of mine started to learn Rust and he found an issue he could not solve on his own.

Consider the following example:

```
fn f(_x: &u32) -> &str {
    "42"
}

fn y(_s: &'static str) { }

fn main() {
    let x = 42;
    let z = f(&x);
    y(z);
}
```

https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=c365c6180c2bb738a7bc70e4a3587f77

Error:

```
error[E0597]: `x` does not live long enough
  --> src/main.rs:9:15
   |
9  |     let z = f(&x);
   |             --^^-
   |             | |
   |             | borrowed value does not live long enough
   |             argument requires that `x` is borrowed for `'static`
10 |     y(z);
11 | }
   | - `x` dropped here while still borrowed
```

I believe the reason he got this error is because lifetime elision inserted a hidden lifetime into `fn f(&u32) -> &str` -> `fn f<'a>(&'a u32) -> &'a str`. However we know that these references are hardly connected.

Instead of error `argument requires that `x` is borrowed for 'static` I would expect to see a helpful suggestion to add `'static` lifetime to a return reference: `fn f(_x: &u32) -> &'static str`.


```
rustc --version
1.43.0
```
Repository: electron
Issue: Support keyboard shortcuts for PDF zooming
Labels: bug :beetle:,component/pdf-viewer,status/confirmed,9-x-y,10-x-y

<!--  As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->

### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->

* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

### Problem Description
It seems that the only way to zoom in/out of document within PDF viewer is to click the `+` and `-` buttons in the lower right.

![image](https://user-images.githubusercontent.com/8367927/80915252-e71cd200-8d05-11ea-9b07-541dda79fe8d.png)

It would be nice if user could also use `⌘+` and `⌘-` (or `CTRL+` / `CTRL-` on Windows). These keyboard shortcuts are supported in Chrome. E.g. https://www.fabfilter.com/help/ffproq3-manual.pdf

### Proposed Solution
Implement above-stated keyboard shortcuts for document zooming.

### Alternatives Considered
None.

### Additional Information
I assume it would make sense for this issue to be tagged similarly to these issues: https://github.com/electron/electron/labels/component%2Fpdf-viewer

---

I tried enabling page zooming via standard View menu in an Electron app I'm working on (`10.0.0-nightly.20200221`, Mac OS 10.14.6). That did allow for page zooming, but the pdf loaded into an `<embed>` tag did not appear to be affected when the embed was focused and I was zooming in/out with keyboard shortcuts. The non-Electron web version of my app (same code minus Electron wrapper) zooms as expected when opened in Chrome.
Repository: godot
Issue: VisualScript. Pool Array functions without sequence port
Labels: bug,topic:editor,topic:visualscript

**Godot version:**
3.2.1 Stable

**OS/device including version:**
Windows 10 64 bit

**Issue description:**

I think there's a problem in visual script with pool array variables. If you want to remove, add, insert, values to an existing pool array variable, and you add the functions "Pool XXXXXX array remove", "Pool XXXXXX array append", etc, you will notice that there is no sequence port and no output data port.

![Poolvector](https://user-images.githubusercontent.com/33732701/80916795-4527d480-8d5b-11ea-9405-4b3e62cec782.png)
Repository: go
Issue: proposal: cmd/vet: Should check for assignments to inbuilt types
Labels: Proposal,Analysis

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.2 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes 


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/thomas/Library/Caches/go-build"
GOENV="/Users/thomas/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/thomas/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.14.2_1/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.14.2_1/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/l5/501mrll12w33yh9vjvlvzfjc0000gn/T/go-build233345544=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I was doing some code review and noticed the snippet:
```go
// ...

s, nil := a()
if err != nil {
    return err
}

// ... 

return nil
```

### What did you expect to see?

`go vet` to give some warnings for assignments to inbuilt types such `nil`, `true`, `false`, etc...

### What did you see instead?

No warnings, and hard to read code.
Repository: pytorch
Issue: torch.cdist returns inconsistent result
Labels: module: numerical-stability,module: docs,triaged,module: distance functions

```python
import torch

A, B = map(torch.load('bug.pt').get, ['A', 'B'])
print(A.shape, B.shape) # torch.Size([95, 39]) torch.Size([295, 39])

D = torch.cdist(A, B)
print(D[75, 233]) # tensor(0., grad_fn=<SelectBackward>)

D_ = torch.cdist(A[75].unsqueeze(0), B[233].unsqueeze(0)).squeeze()
print(D_) # tensor(0.0004, grad_fn=<SqueezeBackward0>)
```
Both ways should have same precision properties. It is very strange that they return different results: 0.0004 is quite a large difference


[bug.pt.gz](https://github.com/pytorch/pytorch/files/4570875/bug.pt.gz)




cc @jlin27 @mruberry
Repository: rust
Issue: Reuse LTO products for incremental builds when deps are unchanged
Labels: A-linkage,C-enhancement,I-compiletime,T-compiler

Incremental builds with LTO (`thin` or `fat`) always take the same amount of time (~10s on [my project](https://github.com/fenollp/reMarkable-tools/tree/730e3fc2c100a713abdeebeb434a9d86aa2a48cc/marauder)) when dependencies are unchanged. It seems to take as long when adding a dependency.

Is it not possible to cache (at least part) of the LTO computations?

Note I'm using `cross`:
```
# cross version
cargo 1.44.0-nightly (8751eb301 2020-04-21)
```
Note also this bug I've encountered WRT LTO: https://github.com/rust-embedded/cross/issues/416

https://github.com/rust-lang/rust/issues/71248 is the most recent issue I could find that seems related.
Repository: rust
Issue: Trait and function bounds checking differ
Labels: A-type-system,A-trait-system,T-compiler,C-bug,T-types

The reproducer is here:
```rust
use std::fmt::Debug;

pub trait Trait {
    fn do_stuff(self) -> ();
}

impl<F> Trait for F
where
    F: 'static + for<'a> Fn(&'a ()) -> Box<dyn 'a + Debug>,
{
    fn do_stuff(self) -> () {
        ()
    }
}

pub fn foo() {
    fn assert_type<F>(f: F) -> F
    where
        F: 'static + for<'a> Fn(&'a ()) -> Box<dyn 'a + Debug>,
    {
        f
    }
    // Compiles
    Trait::do_stuff(assert_type(|_: &()| Box::new(())));
    // Doesn't compile
    Trait::do_stuff(|_: &()| Box::new(()));
}
```
[(playground link)](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=2030c96a7e797153b4113f206a446b9c)

Apparently, adding `assert_type()` around the closure does pass the function bounds. However, when it's not there, the closure doesn't pass the trait bounds despite them being the same.

Most surprising as an end-user (though I guess not that unexpected from an implementation point of view, as we force the bounds in another way), adding the `assert_type` makes the trait bounds pass.

The issue is, of course, that I have to have a `T: Trait` and then call the trait function on it -- ideally without having to manually wrap with `assert_type` at every place where `T: Trait` is taken as an argument, as it'd require a different `assert_type` function per implementor of `Trait`.

(for some more context, this arose with futures instead of `Debug`, but as it reproduced just as well with `Debug` I figured it'd be a better choice than having it be `Future`, to reduce complexity of the example)
Repository: vscode
Issue: Add support for `.XCompose`
Labels: feature-request,editor-input

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: Insiders ece7aaee [snap]
- OS Version: Ubuntu 20.04 LTS

ETA: Also occurs in latest stable (specifically ff915844 [snap])

Steps to Reproduce:

1. `echo include \"%L\" > .XCompose`
2. `echo <Multi_key> <t> <h> <e> <r> <e> <f> <o> <r> <e> : "∴" >> .XCompose`
3. Launch visual studio code.
4. In the main text editor (new file), `<compose>therefore` produces `þerefore`, and in addition `<compose>` by itself is missing its indicator (image 1). In integrated terminal, `<compose>the` produces `he`, still missing the indicator.

Images:
![Caret in chrome](https://user-images.githubusercontent.com/16487249/80920109-8de48b00-8d65-11ea-8e9f-f20403ad897e.png)
![`<compose>therefor` in chrome](https://user-images.githubusercontent.com/16487249/80920145-cbe1af00-8d65-11ea-9d06-0779ae0b7b12.png)

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

Expected vs produced:
`∴` vs information in 4
Repository: flutter
Issue: showTimePicker lacks lastTime option
Labels: c: new feature,framework,f: material design,f: date/time picker,c: proposal,P3,workaround available,team-design,triaged-design

showDateTime method does have a lastDate argument, however showTimePicker does not. This would benefit cases where e.g. user shouldn't be allowed to pick a delivery time after work hours.

```
gintas-mac:domukpizzaapp gintas$ flutter doctor -v
[✓] Flutter (Channel master, 1.18.0-9.0.pre.98, on Mac OS X 10.15.4 19E287, locale en-GB)
    • Flutter version 1.18.0-9.0.pre.98 at /Users/gintas/flutter
    • Framework revision a32c8e84bd (9 hours ago), 2020-05-03 05:54:01 -0400
    • Engine revision e3cb6812ed
    • Dart version 2.9.0 (build 2.9.0-5.0.dev c3ce873556)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/gintas/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[!] VS Code (version 1.43.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • macOS      • macOS      • darwin-x64     • Mac OS X 10.15.4 19E287
    • Web Server • web-server • web-javascript • Flutter Tools
    • Chrome     • chrome     • web-javascript • Google Chrome 81.0.4044.129

! Doctor found issues in 1 category.
```
Repository: neovim
Issue: sessionoptions: allow exclude nofile buffers from save 
Labels: enhancement

### Actual behaviour
Currently (`neovim-0.5.0+ubuntu1+git202005022020-d13c164-00e710e`) `mksession` does not allow exclude `nofile` buffers (NERDTree windows for example) using `sessionoptions`. 
### Expected behaviour
Nothing more than the title says.