pwman

Check-in [db8bd43770]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:index on tweaks: 98593a8 Extend the "don't overwrite fields if only carriage return is entered" to password field
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk | refs/stash
Files: files | file ages | folders
SHA3-256: db8bd437705ecc9803d9f302946d0d0bd2cec929b0945d6c1f6c44b180b00818
User & Date: base@atomicules.co.uk 2014-01-03 22:25:40
Original User & Date: base@atomicules.co.uk 2014-01-03 22:25:41
Context
2014-01-03
22:25
WIP on tweaks: 98593a8 Extend the "don't overwrite fields if only carriage return is entered" to password field Leaf check-in: 4a8cb3e9a0 user: base@atomicules.co.uk tags: trunk, refs/stash
22:25
index on tweaks: 98593a8 Extend the "don't overwrite fields if only carriage return is entered" to password field check-in: db8bd43770 user: base@atomicules.co.uk tags: trunk, refs/stash
2013-03-23
21:27
Extend the "don't overwrite fields if only carriage return is entered" to password field

And also use malloc. What I'd done before wasn't doing what I thought. C
newbie and all that. It must have picked up whatever `input` was
initialised at, which must be one of STRING_SHORT, STRING_MEDIUM, etc.
So it was just by luck it was working. It could have ended up truncating
strings I guess?

I'm in two minds about the benefit of dynamic allocation though. Since
this is hardly a big memory hungry application I could probably just
set `oldinput` to the largest possible string length and it'd be fine. check-in: 378769ec43 user: atomicules@lavabit.com tags: origin/tweaks, trunk

Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch