<feed xmlns='http://www.w3.org/2005/Atom'>
<title>forks/toybox/toys, branch 0.8.2</title>
<subtitle>Toybox with POSIX patches from E5ten
</subtitle>
<id>https://git.carbslinux.org/forks/toybox/atom?h=0.8.2</id>
<link rel='self' href='https://git.carbslinux.org/forks/toybox/atom?h=0.8.2'/>
<link rel='alternate' type='text/html' href='https://git.carbslinux.org/forks/toybox/'/>
<updated>2019-10-17T21:03:18+00:00</updated>
<entry>
<title>ls: Ensure file names are separated by 2 spaces</title>
<updated>2019-10-17T21:03:18+00:00</updated>
<author>
<name>Andrew Ilijic</name>
<email>ilijic.andrew@gmail.com</email>
</author>
<published>2019-10-17T15:03:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.carbslinux.org/forks/toybox/commit/?id=0b34a5637d91428ef5d87769a4c2698d7a1c2b0f'/>
<id>urn:sha1:0b34a5637d91428ef5d87769a4c2698d7a1c2b0f</id>
<content type='text'>
We need two spaces between filenames because that is the convention
followed by other implementations. More importantly, if we do not have
two spaces, certain Unicode file names cause filenames to run together.
In Unicode, combining characters come before the character they modify.
If a filename ends in a combining character, the combining character
attaches to the space that follows it, causing the space not to be
visible. Having a two-space gap stops the above issue from happening.

For context and a bit more information, see mailing list link below.
https://www.mail-archive.com/toybox@lists.landley.net/msg05986.html
</content>
</entry>
<entry>
<title>In-passing cleanup and add a NOP -P.</title>
<updated>2019-10-16T01:00:51+00:00</updated>
<author>
<name>Rob Landley</name>
<email>rob@landley.net</email>
</author>
<published>2019-10-16T01:00:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.carbslinux.org/forks/toybox/commit/?id=89a8d00e470f1999a62ceea81269af2f39c655ba'/>
<id>urn:sha1:89a8d00e470f1999a62ceea81269af2f39c655ba</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Make cmp work with 1 argument (implicit - as second argument).</title>
<updated>2019-10-14T21:13:01+00:00</updated>
<author>
<name>Rob Landley</name>
<email>rob@landley.net</email>
</author>
<published>2019-10-14T21:13:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.carbslinux.org/forks/toybox/commit/?id=ae572524341c427b1f551ea4074a8c1d3d808681'/>
<id>urn:sha1:ae572524341c427b1f551ea4074a8c1d3d808681</id>
<content type='text'>
</content>
</entry>
<entry>
<title>losetup: Fix null-termination of src string instead of dest after copy</title>
<updated>2019-10-14T20:28:28+00:00</updated>
<author>
<name>Alessio Balsini</name>
<email>balsini@android.com</email>
</author>
<published>2019-10-14T16:06:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.carbslinux.org/forks/toybox/commit/?id=0bcd6c10f7d227f335342bda8b2ffced785f2514'/>
<id>urn:sha1:0bcd6c10f7d227f335342bda8b2ffced785f2514</id>
<content type='text'>
The function loopback_setup(), after copying the loopback device name
with xstrncpy(), ensures the null-termination of the string by forcing
its last byte to 0.

Unfortunately, this operation:
- was probably intended to null-terminate dest instead;
- does not affect the program execution because src is free()d right
  after;
- if the size of src is smaller than the offset of the written zero, it
  modifies an unknown byte in the heap.

Drop the null-termination line to fix the issue: xstrcpy() automatically
null-terminates dest, or fails if the size of src is bigger than the the
requested number of bytes to copy.

Signed-off-by: Alessio Balsini &lt;balsini@android.com&gt;
</content>
</entry>
<entry>
<title>Don't need the second variable, and put the comment back.</title>
<updated>2019-10-12T22:24:26+00:00</updated>
<author>
<name>Rob Landley</name>
<email>rob@landley.net</email>
</author>
<published>2019-10-12T22:24:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.carbslinux.org/forks/toybox/commit/?id=f69ca9e9d29c9dfde2860f7d60d57fdbfde856a0'/>
<id>urn:sha1:f69ca9e9d29c9dfde2860f7d60d57fdbfde856a0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix argless find segfault.</title>
<updated>2019-10-12T22:23:30+00:00</updated>
<author>
<name>Denys Nykula</name>
<email>nykula@ukr.net</email>
</author>
<published>2019-10-11T16:09:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.carbslinux.org/forks/toybox/commit/?id=0cc9d996ed3fe49b34fdf0943523e880203e5be5'/>
<id>urn:sha1:0cc9d996ed3fe49b34fdf0943523e880203e5be5</id>
<content type='text'>
Inline array becomes garbage outside the if.
</content>
</entry>
<entry>
<title>hostname: fix error reporting.</title>
<updated>2019-10-12T22:15:54+00:00</updated>
<author>
<name>Elliott Hughes</name>
<email>enh@google.com</email>
</author>
<published>2019-10-10T21:12:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.carbslinux.org/forks/toybox/commit/?id=7adff6b2cad30de073fb597cd0d10826067965ad'/>
<id>urn:sha1:7adff6b2cad30de073fb597cd0d10826067965ad</id>
<content type='text'>
The &lt;netdb.h&gt; functions have their own errno :-(
</content>
</entry>
<entry>
<title>xargs: various fixes.</title>
<updated>2019-10-10T02:24:15+00:00</updated>
<author>
<name>Elliott Hughes</name>
<email>enh@google.com</email>
</author>
<published>2019-10-09T21:48:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.carbslinux.org/forks/toybox/commit/?id=48d750ca5be4db45a3f04956a9d8ca87ddc45db2'/>
<id>urn:sha1:48d750ca5be4db45a3f04956a9d8ca87ddc45db2</id>
<content type='text'>
Don't run the command with no arguments if we run out of input but
have already run the command at least once. The implementation of "run
the command at least once (unless -r was supplied)" wasn't taking into
account whether or not this was our first time round the loop.

Fix the exit value, and the -- already documented but not implemented --
behavior if a child exits with status 255.

Also extend the tests to cover these cases, plus cases I broke while
coming up with the fix. Add more tests to convince myself that we've
correctly interpreted how -s is supposed to behave, and fix the corner
cases at the bottom end of the range.

This fixes some issues we were seeing trying to build the Android SDK
for (and more importantly, on) macOS.
</content>
</entry>
<entry>
<title>ls: fix seqfault on broken locale</title>
<updated>2019-10-10T02:18:30+00:00</updated>
<author>
<name>Jarno Mäkipää</name>
<email>jmakip87@gmail.com</email>
</author>
<published>2019-10-09T21:06:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.carbslinux.org/forks/toybox/commit/?id=52422388520e4bf82e56a4cce3f2c2076cbed834'/>
<id>urn:sha1:52422388520e4bf82e56a4cce3f2c2076cbed834</id>
<content type='text'>
When user builds toybox CFG_TOYBOX_I18N disabled and tries to list
folder contents with multibyte characters other than UTF-8 ls might
seqfault since wcrtomb returns -1

while locale set to fi_FI-UTF-8 disable CFG_TOYBOX_I18N

touch őőőőaaőő
ls
</content>
</entry>
<entry>
<title>vi: fixes</title>
<updated>2019-10-10T02:17:53+00:00</updated>
<author>
<name>Jarno Mäkipää</name>
<email>jmakip87@gmail.com</email>
</author>
<published>2019-10-07T18:22:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.carbslinux.org/forks/toybox/commit/?id=8440d9b29fa8faed432bb20ec031bb5e72f0bea9'/>
<id>urn:sha1:8440d9b29fa8faed432bb20ec031bb5e72f0bea9</id>
<content type='text'>
fix: force redraw after :set (no)list
fix: force redraw after insert
fix: split on zero cursor position
fix: yank and push with utf-8 content
</content>
</entry>
</feed>
