Douglas
Douglas
Sorry for the delay here. While I think this section of the doc needs work, I'm not sure about having a project in a non-Nushell repo is the right way...
I know this goes beyond simple "renaming", but it would be kind of nice if `slice` (agree with the name) worked on both `list` and `string`. This would consolidate `range`...
Sorry for late reply, but yes, you're probably right about the different flags being a good reason to keep these separate.
On the bright side: ```nu 2.10 in 1..1.1..3 # => true ``` > Maybe it can be shipped like this, the REPL already has floating point errors (`1.1 - 1`...
Btw, I've tested the PR and it works as advertised ;-)
This makes modifying an SVG file via `to/from xml` pretty nigh impossible currently. ```nu open foo.svg | from xml | update attributes { upsert width { "100%" } | upsert...
For some reason I thought this has been merged already - I checked last week and must have missed it still being open. @jesper-olsen The operator precedence has changed slightly...
Up to @fdncred but I think we're probably too close (2 days) to next release to have a command in the code that simply errors. It *would* be more convenient...
Right - I can always just checkout the commit with the fix to test.
> Because IDs are a part of history I'm not sure I understand this. In a text-backed history, it's simply a flat-file with no indices. Deleting a history item changes...