newt alternatives and similar packages
Based on the "Tools" category.
Alternatively, view newt alternatives based on common mentions on social networks and blogs.
master-plan9.2 0.0 newt VS master-planProject Management for Hackers
stutter7.7 0.0 newt VS stutterCLI string generator based on regex-like operations
lightstep-haskell7.2 5.4 newt VS lightstep-haskellLightStep OpenTracing client library
nemesis7.2 2.3 newt VS nemesisa task management tool for Haskell
crackNum7.1 0.0 newt VS crackNumConvert to/from IEEE-754 HP/SP/DP formats
cabal-db6.9 0.0 newt VS cabal-dbVarious cabal query commands wrapped in a simple CLI tool
fswatcher6.8 0.0 newt VS fswatcherA simple file/directory watcher for Linux and macOS and other BSDs
technique5.1 0.0 newt VS techniqueCheck, simulate, and run procedures written in the Technique programming language
gt-tools4.9 0.0 newt VS gt-toolsGoogle Translate Console (Haskell)
gsmenu4.5 3.2 newt VS gsmenuA visual generic menu program.
runhs4.5 0.0 newt VS runhsStack wrapper for single-file Haskell programs.
FloatingHex4.0 0.0 newt VS FloatingHexHexadecimal Floats for Haskell
gitcache4.0 0.0 newt VS gitcachesimple git clone cache use and management tool
fswait3.7 0.0 newt VS fswaitWait and observe events on the filesystem for a path, with a timeout
g-npm3.2 0.0 newt VS g-npmTool to create ebuild from npm packages.
shift2.5 1.3 newt VS shiftFork of teleport
hsmodetweaks2.1 0.0 newt VS hsmodetweaksTool for generating .dir-locals.el for intero
imgur1.6 0.0 newt VS imgurA haskell function to post an image to imgur
binsm1.6 0.0 newt VS binsmbinary files splitter and merger, makes working with offsets in your shell less painful
posplyu1.6 0.0 newt VS posplyuSleep tracker for X11, using XScreenSaver extension and manual input.
setop0.7 0.0 newt VS setopPerform set operations on files
Monadoro- - newt VS MonadoroA minimalistic CLI Pomodoro timer, based on a library of the same purpose.
Static code analysis for 29 languages.
Do you think we are missing an alternative of newt or a related project?
Newt is a trivially simple template instantianion tool. WTF is a template instatiotion tool? It turns files with named fields into files without named fields!
Say you just spent twelve hours Yak-shaving to get a configuration file tweaked just right, and your friends want to use it. However, the configuration file has your user name and password in it, so you can't just share the file with them. At the very least, you have to replace those values, then tell your friends where to put their values, and hopefully those only occurr once in the file you need to share.
Newt can make this easier.
Here's what you do:
- make a copy of your config file somewhere so you don't break the one you actually use.
- replace your user name with the string
- replace your password with the string
Now, send your friends the new file with these instructions:
- Go install newt!
- Save this template to /tmp/myTemplate
newt --source=/tmp/myTemplate --dest=<destination> username=yourUsername password=yourPassword
- Alternatively, you can leave off the
newt /tmp/myTemplate <destination> username=yourUsername password=yourPassword
- Alternatively, you can leave off the
- There you go.
<destination>now has a populated version of the config file.
I did say Newt was trivially simple.
Aside from usernames and passwords, you can use newt to replace any string key with any string value, as long as none of the keys include ">>>" or "=". It might even handle unicode someday.
I hope this is handy for writing scripts that need to set configuration files, or if you write a lot of LaTeX documents, and you want to fill in boiler plate from a command line. I also have grand design for pointing newt at a tarball of templates and having it expand the tarball while fleshing out the details. For now, you get to work with one file at a time.
Create a new cabal project!
Input File (
name: <<<name>>> version: 0.0.0.1 synopsis: <<<synopsis>>> description: <<<description>>> category: Tools license: BSD3 License-file: LICENSE author: <<<author>>> maintainer: <<<authoremail>>> Cabal-Version: >=188.8.131.52 build-type: Simple Executable <<<name>>> Main-Is: Main.hs hs-source-dirs: src
$ newt --source=in.cabal --dest=FooApp.cabal name=FooApp author="Rogan Creswick" [email protected]
Result (in FooApp.cabal):
name: FooApp version: 0.0.0.1 synopsis: <<<synopsis>>> description: <<<description>>> category: Tools license: BSD3 License-file: LICENSE author: Rogan Creswick maintainer: [email protected] Cabal-Version: >=184.108.40.206 build-type: Simple Executable FooApp Main-Is: Main.hs hs-source-dirs: src
Note that the author needed to be put in quotes to prevent the shell from splitting the
author="Rogan Creswick" argument to Newt into two arguments.
Also note that we didn't need to define
description. They remain in the file, so you can partially fill a template if you want.
List the keys
Newt can also tell you which keys you can specify for a given
template. If you don't know what the valid keys are, then just run
$ newt --source=in.cabal --list author authoremail description name synopsis
*Note that all licence references and agreements mentioned in the newt README section above are relevant to that project's source code only.