-
```
What steps will reproduce the problem?
1. Put the following in a buffer:
var viewPanel = new Ext.Panel({
frame:true,
title: 'Search',
items: [fooPanel, taskActions]
});
2. Put the cur…
-
```
What steps will reproduce the problem?
1. Put the following in a buffer:
var viewPanel = new Ext.Panel({
frame:true,
title: 'Search',
items: [fooPanel, taskActions]
});
2. Put the cur…
-
According to docstring `M-x sp-clone-sexp RET` on `(| ())` should yield
```
( ())
( ())
```
because point is two spaces before an sexp, i.e. not immediately before. But the actual behavior res…
whxvd updated
5 years ago
-
Right now, `Sexp#line` can be used to either fetch or set the line number. This has led to some bugs which were addressed by https://github.com/seattlerb/sexp_processor/commit/ce284487f057203360c41b14…
-
I find this behaviour frustrating. There is a way to disable it?
-
```
What steps will reproduce the problem?
1. Put the following in a buffer:
var viewPanel = new Ext.Panel({
frame:true,
title: 'Search',
items: [fooPanel, taskActions]
});
2. Put the cur…
-
```
What steps will reproduce the problem?
1. Put the following in a buffer:
var viewPanel = new Ext.Panel({
frame:true,
title: 'Search',
items: [fooPanel, taskActions]
});
2. Put the cur…
-
Sometimes, a ship might want to change its name.
Turns out, scripting can do that already. Buuut, caveat: You need to refer to the ship in question through when-argument SEXPs going forward, as you n…
-
Currently, we create a **SExp** from a token in the parser. But, the **primitives**, like '+', need to return a new **SExp** (It should not has location information). So, I suggest to reconstruct the …
-
```
What steps will reproduce the problem?
1. Put the following in a buffer:
var viewPanel = new Ext.Panel({
frame:true,
title: 'Search',
items: [fooPanel, taskActions]
});
2. Put the cur…