Hacker News new | past | comments | ask | show | jobs | submit | fredrikfornwall's comments login

The situation is actually not that bad - see https://www.reddit.com/r/termux/comments/1dbujal/information... for more follow-up information.

TL;DR: Termux is coming back to Google Play! While it's currently missing some features and have some rough edges due to more restrictive Google Play requirements and feedback from the review process, it will be fleshed out over time.


A properly written trigger shouldn't throw away data silently.

It should raise an exception, which indeed would cause the query to fail, and roll back the whole transaction (so no side effect is committed at all).

https://www.postgresql.org/docs/current/static/plpgsql-error...


Note that you can use mosh on Android using Termux (https://termux.com) - run 'apt update && apt install mosh' to install the mosh package.


When you 'apt install coreutils' in Termux you get coreutils installed as a multi-call binary to save space. 1556 kB for the package in total (including man pages).


Thanks! Is it the make program itself which tries to run /bin/sh, or does it try to run a file from a project which has a #!/bin/sh start?

If it's GNU make itself which tries to call /bin/sh directly, that could be patched from my side. But if it is a script from a file, you have to make the shebang replacement #!/bin/sh -> #!${PREFIX}/bin/sh yourself on all script files to be executed - there is a simple termux-fix-shebang script installed by default for that!


I've tryed it on a very simple makefile and after some testing found what trigger the message. It is simply a line with an "echo" command. It seems that make try to run it with "/bin/sh".


Thanks - this is now fixed, if you do an 'apt update && apt upgrade' it should now work!


Thanks, it works perfectly now.

Do you plan to also make a version for 64bit ARM ? This one works perfectly on my Nexus 9 but I would love to be able to develop for ARM64 directly on it.

Thank you for your work, From what I see on the play store, you plan to make money with the extensions ? I will probably buy at least the theme one soon.


Great! Yes, I've been experimenting with ARM64 packages, will look at it more when things settle down a bit.

Nice, let me know if there is a font or colour theme you miss from it!


Thanks, KBOX have been one of the inspirations for the app!

The main technical difference between how Termux and KBOX runs packages is that is that KBOX uses libfakechroot for running binaries under a fake chroot environment, while Termux runs without a chroot, having instead patched the packages to live under the file system hierarchy enforced by Android.

Besides that, the ambition is that Termux should give a more "out of the box" user friendly experience directly after installation to encourage newcomers to the world of terminals :).


How does this compare to TerminalIDE? I'll try this out and KBOX too for myself. Thanks!


I think TerminalIDE is rather similar, with Termux having more up-to-date packages and terminal emulation.

Since Termux requires Lollipop or later, and TerminalIDE only works on Android versions prior to lollipop, TerminalIDE could be an alternative for devices running older Android versions.

Thanks for trying it out - let me know if you have any suggestions for improving the app!


I tried 'apt-get install' by mistake. I see your help file uses 'apt install'. I tried 'apt install picolisp', but no luck. Do you have your own package repository? Thanks.


Yes, the repository is an app-specific one, containing cross compiled (and sometimes patched) packages to run directly without chroot. Just tell me about desired packages (such as picolisp) and I will look into adding them!


So how well does this work under secondary users? AFAIK /data/data always points to the primary user's data directory, so this wouldn't quite work...


Correct, it won't work for secondary users! It's a trade-off for avoiding a fake chroot.


Thanks! I'll think about making the source more obvious in the store listing or the app interface.


Yes, Android 5.0 or later is required due to the libc changes made in lollipop. It also requires an arm(64) or x86(_64) cpu - no mips support at the moment!


Finally updated my note3 to lollipop - I like your price point for the theme-addon. Bought it. Keep up the good work! :)


Great, thanks :). Let me know if you miss any font or colour theme from it!


Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: