CLI Discussions Resources

Discuss anything related to command line tools here.
Post Reply
Message
Author
vevy
Posts: 681
Joined: Tue Sep 10, 2019 11:17 am

CLI Discussions Resources

#1 Post by vevy » Sun Oct 11, 2020 8:43 pm

Since the first post is getting a bit too big and unwieldy to edit, I made this thread to help simplify things.

The discussion is still there!

Earlier versions of the 1st post
Spoiler!   
To help keep both databases with a unified code base from the start, I made this table to higlight similarities/differences and keep things more manageable.
Property Main Database CLI Database Notes
Existing Fields:
Software title (Required)License (Required) Enabled Enabled
Categories (Required) Enabled Enabled Two-level main categories in both.
Website URL (Required) Enabled Enabled Some tools may not have one site (e.g. Unix tool ports).
Size (in bytes) (Required) Enabled Enabled Some tools have variable sizes depending on features (e.g. Cygwin, Yori). Workaround: enter "0".
License (Required) Enabled Enabled
System requirements (Required) Enabled Enabled
Description (Required) Enabled Enabled
Writes settings to (Required) Enabled Enabled
How to extract (Required) Enabled Enabled Needs a template for CLI tools (Add to PATH, launch in console, etc).
Version number (Optional) Enabled Enabled
Download URL (Optional) Enabled Enabled Some tools are only downloadable as a part of a collection. Solution: Leave empty.
Icon (Optional) Enabled ? Most CLI tools don't have icons.
Screenshot (Optional) Enabled ? Can be a screenshot of help/usage.
Additional Features (Optional) Enabled Disabled? See proposed system.
Additional status (Optional) Enabled Enabled? We need to discuss adware in CLI tools.
Path portability (Optional) Enabled Enabled Is it a given in CLI tools?
Unicode support (Optional) Enabled Enabled
Dependencies (Optional) Enabled Enabled
Stealth (Optional) Enabled Enabled
Keywords (Optional) Enabled Enabled
Forum topic ID (Optional) Enabled Enabled
Similar/alternative apps (Optional) Enabled ? Replaceable with function tags?
Suggested by (Optional) Enabled Enabled
Release date (Optional) Enabled Enabled
Proposed Fields:
Functions ? Enabled see discussion
Part of Disabled Enabled For tools that come under a main tool/collection. (child)
Parts Disabled Enabled For the collections that contain multiple tools. (parent)
Editor's Pick Enabled? Enabled For the excellent tools that deserve to be highlighted.
Documentation/Link to Documentation Disabled Enabled?

Spoiler!   
Standing requests:
  • Allow child entries to get details from parent tool (collection): (Andrew: Done)
    • The reasoning for this is:
      • Avoid entering (and updating) the same information in hundreds of child tools.
      • Allow filtering by this criteria. If we simply leave these fields empty in the child tools, they won't show on filtering by these criteria. For example, open-source tools that are updated after 2019-01-01 with use case X.
    • Entering entry id for collection in a field instructs TPFC to grab the details of this field from the parent collection.
    • For example, a release date of "{app=13}" means has the same release date of entry #13.
    • If the release date of app #13 (the parent collection) is updated, this gets reflected in all child entries.
    • Method #2 If it is difficult to change the type of the current fields (like release date), you can:
      • Create a general field for "Parent entry ID".
      • For each needed field (like release date), create a checkbox to use that of parent instead. Select which to use (the original filed or the checkbox) using radio buttons (i.e. make them mutually exclusive).
  • New fields:
    • IsWarningNet (Boolean) field (optional).
    • IsWarningDecompression (Boolean) field (optional).
    • IsWarningSecurity (Boolean) field (optional).
    • IsNotArchiver (Boolean) field (optional).
    • IsNotCompressor (Boolean) field (optional).
    These fields can be small in space/checkboxes in one line, etc.
  • The table request mentioned here. (Andrew: No solution)

First Post of CLI Database Discussions as of 2020-10-20
Spoiler!   
NOTE: This post refers to and uses elements from CLI Discussions Resources.


Current priorities:
  • Mini-requests
  • #23: Developer field.
  • #43 to #49: Additional statuses.

Mini-requests:
  • Done:
    Spoiler!   
    • ✅ Add [ section ] tag to the entry edit toolbars. (Andrew: Done)
    • ✅ Add color to monospace/code tag and change font to Consolas (like in the forums).(Andrew: Done)
    • ✅ Add already-usable (but hidden) tags to the entry edit toolbars (e.g. color, strike-through) (Andrew: Strikethrough implemented. Color is discouraged.)
    • ✅ System requirements: new option: "Untested". (Andrew: Done)
    • ✅ Rename Open-source checkbox to "Open-source/Public-domain". (Andrew: Done)
    • ✅ Bug: When adding (not editing) an entry, parent ID disappears in preview.
    • ✅ Change "System requirements" name to "OS support".
    • ✅ Make icon conditionally inherited (i.e. if child icon field is empty). (Andrew: Done)
    • ✅ Make sure "Open source/Public domain" status box is inherited with the license field. (Andrew: Done)
    • ✅ Open source checkbox in search should only show tools with checked "Open source/Public domain" box. (Andrew: Just checked; seems to work fine. Pls send details if bug encountered.)
    • ✅ Remove "v" from Version field.(Andrew: Done)
    • ✅ Sidebar (until it is adapted to CLI, perhaps it is better to either correct the links or hide these sections):
      • ✅ Popular titles: entries from regular DB but with ".cli"
      • ✅ Recent comments: same.
      • ✅ Recent updates: same.
  • If an icon file is chosen, there is no way to remove it during adding or editing. Same for screenshot? (Andrew: KIV)
  • [_size] tag should also apply to line spacing. (Andrew: KIV)
  • Links to fix (usually "cli." is unduly added to them): (Andrew: Done)
    • Edit entry: "Portable Freeware Update" Link.
    • DB search: "Forum topics matching your query"
    • ✅ Entry Comments: user profile links.
  • Minor correction to span.use-case: padding: 0px 4px 2px 4px;
  • In edit page, "Beta releases should be posted to..." message should be removed for CLI.
------------------------------------------------------------
Use case and format requests to be added later.

ID Request Description Priority (1=min, 3=max, p=postponed) Andrew: Priority Andrew: Status
General
#1 Clearer edit logs Currently, entry log history is diff-ed by characters, which makes figuring the changes out very difficult. Better do it by filed or paragraph. 2 KIV
#2 Adapt main page links to CLI. Like "About", "Useful Links", etc 2p Updated to point to main site.
#3 Adapt current templates to CLI "How to extract", "Writes settings to", etc 1p KIV
#4 Stock Icon for TUI tools. Image
Free for commercial. Only attribution.
Spoiler!   

Code: Select all

<div>Icons made by <a href="https://www.flaticon.com/authors/flat-icons" title="Flat Icons">Flat Icons</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a></div>
1 KIV
#5 Promote the best tools. Make a system for promoting the better tools (Editor's pick, voting, etc) ? KIV. The star system (currently only activated for main site) is scored based on internal and external voting.
Listings and Filtering/Sorting Filtering on one/combined fields mainly under Detailed Search.
#6 Sorting by last edited Sorting entries by last entry update date (as logged). 2 KIV
#7 Filtering by License e.g. only FOSS results. ✅
#8 Filtering by release date For example, tools released on or after 2018-01-01 1-2 KIV
#9 Filtering by developer All tools by a given developers. Useful for maintenance and usage. 1-2 KIV
#10 Filtering by categories Useful with large categories when combined with other filters. 1-2 KIV
#11 Filtering by use case. -- 2p KIV
#12 Filtering by tool size. -- 1 KIV
#13 Filtering by system requirements. 1p
Spoiler!   
(when such data is entered satisfactorily)
KIV
#14 Filtering by entry type/status Tool, package, Win. package, discontinued, etc. 1-2(p?) KIV
#15 Filtering by dependencies Needs the field to have a Boolean option of Y/N first (like Stealth). Needs the information to be entered first. 1p KIV
#16 Filtering by stealth Needs the data first. 1p KIV
#17 Clickable badges
Spoiler!   
Make badges (additional status/warning) clickable (to a page filtered by these badges e.g. Win packages only). This will have the side benefit of making categories like "Collection" and "Unix Ports" unneeded.
1-2 KIV
#18 Field incomplete message If a filterable field is optional, show a message atop the "filter results page" that says: "Not all tools contain this type of information. Results may be incomplete." KIV
#63 Filter by IsChild Useful for maintenance. KIV
#64 Implement filters as text first. Especially for maintenance filters. e.g. Instead of a checkbox for "Child tool", append "child:1" to search.
mp3 license:foss child:1 extract:"."
Easier to implement (?), less UI clutter.
KIV
Search
#19 One-word synonyms Handle one-word synonyms: like audio=soundmusic. 1p
#20 Handle aliases Use cases like overlay video on another=picture in picture effect and formats like jpg=jpeg. 1-2p
#21 Partial matches. "implement" should also match "implementation". 2p
Spoiler!   
(I'd want it today, but not easily doable; so postponed for now)
#22 Search terms separately i.e. not necessarily in order 2p
New Entry Fields
#23 Developer/Author field (Required) Show suggestion like "Title" field, but clicking a suggestion enters it into the field (not disabled like "Title"). 2-3
#70 Download Link (Archive) (Optional) Archive.org or so in case dev site goes offline. 2
#71 Download Link (Archive) (Optional) Archive.org or so in case dev site goes offline. 2
#24 Documentation Link (Optional) -- 1p
#25 Documentation Text (Optional) Collapsed by default. 1p
#26 IsWarningNet (optional) Boolean. As text or badge with hover text. 1-2
#27 IsWarningSecurity (optional) Boolean. As text or badge with hover text. 1-2
#28 IsWarningDecompression (optional) Boolean. As text or badge with hover text. 1-2
#29 IsNotArchiver (optional)
Spoiler!   
Boolean. As text or badge with hover text. Useful because of the difference in behavior with compression tools in GUI vs CLI.
1
#30 IsNotCompressor (optional)
Spoiler!   
Boolean. As text or badge with hover text. Useful because of the difference in behavior with compression tools in GUI vs CLI.
1
#31 Blurb (optional) One-liner like GNU blurbs, Debian package desc. 1
#32 IsInIndex Boolean, optional. Added to the CLI Tool Index or not. Useful for managing the additions of tools. 1-2p
#33 Available in/Part of/Get it from/Parent Entry: Optional. Still WIP.
Enter delimited IDs of parent tools, e.g. 6,9,11 Will put a field with sentence: Available in UnxUtils, GnuWin, Gow.
2p
#34 Notes (Optional) Edit box. Not shown in entry view.
#51 GUI Front-ends Edit box. Optional. Link or just name the front-ends available for a tool. 1-2
Existing Fields
#35 Software title: Suggestions To avoid duplicate entries. Make suggestions clickable into a new tab. ✅
#36 Move Additional statuses Next to the title. This should better help clarity and will save space. ✅ Done
#52 How to extract: "Standard extraction"
Spoiler!   
Add the following template (in code) to the extraction field.
Most CLI tools are in simple archives. No need to add the full instructions to each entry because:
1. They don't really change.
2. They'll take space.
3. This allows unification and improving the instructions or adding more/better examples at any time.

Code: Select all

[url=https://www.portablefreeware.com/forums/viewtopic.php?t=25028&p=97047#p97047][size=2][color=grey][u]Standard extraction[/u][/color][/size][/url]
Image
0 Done
#53 How to extract: "See parent"
Spoiler!   
Add the following template (in code) to the extraction field.

Code: Select all

[size=2][color=#969696]See parent package(s) or port(s).[/color][/size]
Image
0 Done
#54 Templates as unexpanded tags
Spoiler!   
Going with your suggestion about [warning] tags, and in the same spirit of unifying template wording and facilitating global changes, add templates in general as tags.

e.g. [extraction_see_parent] in #53 and expand automatically.

There are ways to expose the wording to the contributor if you wish to discuss.
2p
#68 "v" in Version field Insert automatically in entry view? 1p
Additional status badges
#37 Package Image ✅
#38 Collection Image ✅
#39 Win Package? same style as "Collection" and "Package" p
#40 Tool Image ✅
#41 Unix Port Image ✅
#42 Discontinued Image ✅
#43 CLI-mode GUI
Image
2-3
#44 TUI
Image
2-3
#45 Batch
Image
2-3
#46 Internal Command/Subcommand
Image or Image
2-3
#47 Windows-Included
Image
2-3
#48 Alternative Shell
Image
2-3
#49 Shell Extension
Image
2-3
Inherited fields
#50 Parent>Child detail inheritance System to allow child entries to get details from parent tool (collection) ✅
#55 Title Possible use: Automatically include parent name between brackets touch [Yori]. 1p
#56 Site URL Always inherited. ✅
#57 Size Conditionally inherited (if child field is empty) ✅
#58 License Conditionally inherited ✅
#59 Runs On Conditionally inherited ✅
#60 Icon Conditionally inherited ✅ Done
#61 Release date Always inherited. ✅
#62 Developer Conditionally inherited? p (implement field first).
#69 Suggested by Conditionally inherited 2
#65 Suggest parent name Upon entering parent ID. 1-2
Use Cases TBC
Formats TBC
Filterable, Sortable Tables
#66 Sources/Developers table All the sources sifted for Windows CLI tools.
These could be developer sites, Github pages, directories, etc.
This allows us to know what was checked and when, and whether it needs to be checked regularly.
2
#67 Index Table Could be dynamically linked to the database or static.
CTRL+F for whether a tool exists in the database and its basic info.
1-2p
------------------------------------------------------------------


Original Post:
Spoiler!   
Hi, everyone

I know Andrew is not big on CLI tools, but they are very useful. I keep discovering new tools and some of them are jaw-dropping in functionality and keep wondering: what else is there that I could be missing?

There are many sites that list CLI software among GUI software. Alternativeto.net has tags that help separate such tools, but their database doesn't have that many.

Also, some software authors have many capable CLI tools on their sites.

What I mean is, they are all-over the place and deserve a separate database.

Is there something like that out there? Eager to here your recommendations (and ideas) :)
Last edited by vevy on Tue Oct 20, 2020 10:00 pm, edited 2 times in total.
"Is there a Windows-included tool for this task?"
"I only want open-source tools"
"I want a tool that is still actively developed"
"So many to choose from!"
and many more!
Support easy-to-do filters and badges!

vevy
Posts: 681
Joined: Tue Sep 10, 2019 11:17 am

Re: CLI Discussions Resources

#2 Post by vevy » Sun Oct 11, 2020 9:05 pm

CSS:

CLI-mode GUI
Image
Spoiler!   

Code: Select all

span.status.gui_cli {
	box-shadow:inset 0px 0px 0px 1px #444;
	border: 1px solid #444;
	color:#F2F0E6;
	text-shadow: -1px 0px 1px  #000, 1px 0px 1px  #000, 0px -1px 1px  #000, 0px 1px 1px #000;
	background:linear-gradient(167deg, #F0F8FF, #F0F8FF 50%, #555 50%, #555);
}
TUI
Image
Spoiler!   

Code: Select all

span.status.tui {
	background-color: #004164;
	border: 1px solid #009CBA;
	border-radius: 0;
	box-shadow:inset 0 0 0 1px #008080, inset 0 4px 0 0 #008080; 
	color: #B8C821;
}
Batch
Image
Spoiler!   

Code: Select all

span.status.batch {
	background-color: white;
	border: 1px solid #0061a7;
	border-radius: 0;
	box-shadow:inset 0 0 0 1px #0061a7, inset 0 4px 0 0 #0061a7; 
	color: #222222;
}
Internal Command
Image
Spoiler!   

Code: Select all

span.status.internal_command {
	background-color: black;
	border: 1px solid #91979E;
	border-radius: 0;
	box-shadow:inset 0 0 0 1px #91979E, inset 0 4px 0 0 #DFE3E6; 
	color: white;
}
Alternatively, Subcommand
Image
Spoiler!   

Code: Select all

span.status.subcommand{
	background-color: black;
	border: 1px solid #91979E;
	border-radius: 0;
	box-shadow:inset 0 0 0 1px #91979E, inset 0 4px 0 0 #DFE3E6; 
	color: white;
}
Windows-Included
Image
Spoiler!   

Code: Select all

span.status.windows_included {
border: 1px solid royalblue;
padding-left: 24px;
background-image:
	linear-gradient(to right, #F35220, #F35220),
	linear-gradient(to right, #7DB606, #7DB606),
	linear-gradient(to right, #05A6F0, #05A6F0),
	linear-gradient(to right, #FFBA08, #FFBA08),
	linear-gradient(to right, #FFFFFF, #FFFFFF);

background-repeat: no-repeat;
background-position:
	1px 1px,
	11px 1px,
	1px 11px,
	11px 11px,
	0,0;

background-size:
	9px 9px,
	9px 9px,
	9px 9px,
	9px 9px,
	100% 100%;
}
Alternative Shell
Image
Spoiler!   

Code: Select all

span.status.alternative_shell {
	background-image:
	linear-gradient(to right, green, green),
	linear-gradient(to right, yellow, yellow),
	linear-gradient(to right, red, red),
	 linear-gradient(to right, rgba(0,0,0,0), rgba(0,0,0,0));
background-repeat: no-repeat;
background-position:
	right 12px top 1px,
	right 7px top 1px,
	right 2px top 1px,
	0 0;
background-size:
	2px 2px,
	2px 2px,
	2px 2px,
	100% 100%;

	background-color: black;
	border: 1px solid #aaaaaa;
	border-radius: 0;
	box-shadow:inset 0 4px 0 0 #aaaaaa88; 
	color: lightgreen;
}
Shell Extension
Image
Spoiler!   

Code: Select all

span.status.shell_extension {
	padding-left: 24px;
	background-image:
	linear-gradient(to right, #ffffff, #ffffff),
		linear-gradient(to right, #ffffff, #ffffff),    
		linear-gradient(to right, #91979E, #91979E),
		linear-gradient(to right, #91979E, #91979E),
		linear-gradient(to right, #91979E, #91979E),
		linear-gradient(to right, #91979E, #91979E),
		linear-gradient(to right, #000000, #000000),
linear-gradient(to right, #000000, #000000),
	linear-gradient(to right, rgba(0,0,0,0), rgba(0,0,0,0));
background-repeat: no-repeat;
border-radius: 0;
background-position:
	10px 8px,
	7px 11px,   
	0px 0px,
	0px 0px,
	19px 0px,
	0px 19px,
	2px 6px,
	0 0;
background-size:
	2px 8px,
	8px 2px,
	20px 6px,
	2px 20px,
	2px 20px,
	21px 2px,
	17px 13px,
	0% 0%;
	background-color: white;
	color: black;
}
Last edited by vevy on Fri Oct 16, 2020 12:24 am, edited 2 times in total.
"Is there a Windows-included tool for this task?"
"I only want open-source tools"
"I want a tool that is still actively developed"
"So many to choose from!"
and many more!
Support easy-to-do filters and badges!

vevy
Posts: 681
Joined: Tue Sep 10, 2019 11:17 am

Re: CLI Discussions Resources

#3 Post by vevy » Fri Oct 16, 2020 12:00 am

Warnings:

  • IsWarningNet: Be careful with network-facing tools. Vulnerabilities are discovered from time to time. Try to keep such tools updated (including any third-party components or DLLs included with them).
    • IsWarningSecurity: Be careful with security tools. Vulnerabilities are discovered from time to time. Try to keep such tools updated (including any third-party components or DLLs included with them).
      • IsWarningDecompression: Be careful with decompression tools. Vulnerabilities are discovered from time to time. Try to keep such tools updated (including any third-party components or DLLs included with them).
        • IsNotArchiver: This tool does NOT put multiple files into an archive. It just compresses a single file to reduce its size. You may want to group your files first using an archiver. Also, most compressors DELETES the original file by default after compression).
          • IsNotCompressor: This tool only puts multiple files into an archive. It doesn't compress them. You may want to also use a compressor for that..

          Other notes and warnings:
          • Old PNG utilities can't read many new PNG variations.
          Last edited by vevy on Fri Oct 16, 2020 1:17 am, edited 2 times in total.
          "Is there a Windows-included tool for this task?"
          "I only want open-source tools"
          "I want a tool that is still actively developed"
          "So many to choose from!"
          and many more!
          Support easy-to-do filters and badges!

          vevy
          Posts: 681
          Joined: Tue Sep 10, 2019 11:17 am

          Re: CLI Discussions Resources

          #4 Post by vevy » Fri Oct 16, 2020 12:06 am

          Attachments
          Spoiler!   
          Shell Extension.png
          Shell Extension.png (1.67 KiB) Viewed 404 times
          Alternative Shell.png
          Alternative Shell.png (1.84 KiB) Viewed 404 times
          Windows-Included.png
          Windows-Included.png (2.04 KiB) Viewed 404 times
          Internal Command.png
          Internal Command.png (1.66 KiB) Viewed 404 times
          Batch.png
          Batch.png (1.41 KiB) Viewed 404 times
          TUI.png
          TUI.png (741 Bytes) Viewed 404 times
          CLI-mode.png
          CLI-mode.png (2.94 KiB) Viewed 404 times
          discontinued.png
          discontinued.png (977 Bytes) Viewed 404 times
          unix_port.png
          unix_port.png (1.2 KiB) Viewed 404 times
          tool.png
          tool.png (810 Bytes) Viewed 404 times
          collection.png
          collection.png (1.3 KiB) Viewed 404 times
          package.png
          package.png (1.23 KiB) Viewed 404 times
          extraction_see_parent.png
          extraction_see_parent.png (4.24 KiB) Viewed 404 times
          standard-extraction.png
          standard-extraction.png (3.95 KiB) Viewed 404 times
          Subcommand.png
          Subcommand.png (414 Bytes) Viewed 404 times
          TUI_Icon.png
          TUI_Icon.png (2.56 KiB) Viewed 354 times
          discontinued2.png
          discontinued2.png (1.28 KiB) Viewed 237 times
          New.png
          New.png (1.21 KiB) Viewed 81 times

          New:
          Unix_Port.png
          Unix_Port.png (1.84 KiB) Viewed 80 times
          Tool.png
          Tool.png (1.29 KiB) Viewed 80 times
          Package.png
          Package.png (1.82 KiB) Viewed 80 times
          Collection.png
          Collection.png (1.91 KiB) Viewed 80 times
          TUI.png
          TUI.png (1.16 KiB) Viewed 79 times
          Batch.png
          Batch.png (1.11 KiB) Viewed 78 times
          Last edited by vevy on Thu Nov 19, 2020 11:20 am, edited 8 times in total.
          "Is there a Windows-included tool for this task?"
          "I only want open-source tools"
          "I want a tool that is still actively developed"
          "So many to choose from!"
          and many more!
          Support easy-to-do filters and badges!

          vevy
          Posts: 681
          Joined: Tue Sep 10, 2019 11:17 am

          Re: CLI Discussions Resources

          #5 Post by vevy » Tue Oct 20, 2020 9:44 pm

          Old Requests:

          Spoiler!   
          Mini-requests:
          • ✅ Add [ section ] tag to the entry edit toolbars. (Andrew: Done)
          • ✅ Add color to monospace/code tag and change font to Consolas (like in the forums).(Andrew: Done)
          • ✅ Add already-usable (but hidden) tags to the entry edit toolbars (e.g. color, strike-through) (Andrew: Strikethrough implemented. Color is discouraged.)
          • ✅ System requirements: new option: "Untested". (Andrew: Done)
          • ✅ Rename Open-source checkbox to "Open-source/Public-domain". (Andrew: Done)
          • ✅ Bug: When adding (not editing) an entry, parent ID disappears in preview.
          • ✅ Change "System requirements" name to "OS support".
          • ✅ Make icon conditionally inherited (i.e. if child icon field is empty). (Andrew: Done)
          • ✅ Make sure "Open source/Public domain" status box is inherited with the license field. (Andrew: Done)
          • ✅ Open source checkbox in search should only show tools with checked "Open source/Public domain" box. (Andrew: Just checked; seems to work fine. Pls send details if bug encountered.)
          • ✅ Remove "v" from Version field.(Andrew: Done)
          • ✅ Sidebar (until it is adapted to CLI, perhaps it is better to either correct the links or hide these sections):
            • ✅ Popular titles: entries from regular DB but with ".cli"
            • ✅ Recent comments: same.
            • ✅ Recent updates: same.



          ID Request Description Priority (1=min, 3=max, p=postponed) Andrew: Status
          #52 How to extract: "Standard extraction"
          Spoiler!   
          Add the following template (in code) to the extraction field.
          Most CLI tools are in simple archives. No need to add the full instructions to each entry because:
          1. They don't really change.
          2. They'll take space.
          3. This allows unification and improving the instructions or adding more/better examples at any time.

          Code: Select all

          [url=https://www.portablefreeware.com/forums/viewtopic.php?t=25028&p=97047#p97047][size=2][color=grey][u]Standard extraction[/u][/color][/size][/url]
          Image
          0 Done
          #53 How to extract: "See parent"
          Spoiler!   
          Add the following template (in code) to the extraction field.

          Code: Select all

          [size=2][color=#969696]See parent package(s) or port(s).[/color][/size]
          Image
          0 Done
          #3 Adapt current templates to CLI "How to extract", "Writes settings to", etc 1p KIV
          #39 Win Package same style as "Collection" and "Package" 0
          "Is there a Windows-included tool for this task?"
          "I only want open-source tools"
          "I want a tool that is still actively developed"
          "So many to choose from!"
          and many more!
          Support easy-to-do filters and badges!

          Post Reply