You've already forked httpie-cli
							
							
				mirror of
				https://github.com/httpie/cli.git
				synced 2025-10-30 23:47:52 +02:00 
			
		
		
		
	Spelling and bash completion fixes (#1137)
* Remove hashbang from bash completion Completion files are not supposed to have a hashbang. They are sourced, not executed. * Fix spelling * Trim excess whitespace
This commit is contained in:
		
							
								
								
									
										2
									
								
								.github/ISSUE_TEMPLATE/bug_report.md
									
									
									
									
										vendored
									
									
								
							
							
						
						
									
										2
									
								
								.github/ISSUE_TEMPLATE/bug_report.md
									
									
									
									
										vendored
									
									
								
							| @@ -10,7 +10,7 @@ assignees: '' | ||||
| **Checklist** | ||||
|  | ||||
| - [ ] I've searched for similar issues. | ||||
| - [ ] I'm using the the latest version of HTTPie. | ||||
| - [ ] I'm using the latest version of HTTPie. | ||||
|  | ||||
| --- | ||||
|  | ||||
|   | ||||
| @@ -110,7 +110,7 @@ This project adheres to `Semantic Versioning <https://semver.org/>`_. | ||||
|   2. The server handling the request has been modified by an attacker and | ||||
|      instead of the expected response the URL returns a redirect to another | ||||
|      URL, e.g., ``attacker.example.org/.bash_profile``, whose response does | ||||
|      not provide  a ``Content-Disposition`` header (i.e., the base for the | ||||
|      not provide a ``Content-Disposition`` header (i.e., the base for the | ||||
|      generated filename becomes ``.bash_profile`` instead of ``file.txt``). | ||||
|   3. Your current directory doesn’t already contain ``.bash_profile`` | ||||
|      (i.e., no unique suffix is added to the generated filename). | ||||
| @@ -286,7 +286,7 @@ This project adheres to `Semantic Versioning <https://semver.org/>`_. | ||||
|  | ||||
| * XML data is now formatted | ||||
| * ``--session`` and ``--session-read-only`` now also accept paths to | ||||
|   session files (eg. ``http --session=/tmp/session.json example.org``) | ||||
|   session files (e.g. ``http --session=/tmp/session.json example.org``) | ||||
|  | ||||
|  | ||||
| `0.5.1`_ (2013-05-13) | ||||
|   | ||||
| @@ -25,7 +25,7 @@ to your bug report, e.g.: | ||||
| ============================= | ||||
|  | ||||
| Before working on a new feature or a bug, please browse `existing issues`_ | ||||
| to see whether it has previously  been discussed. | ||||
| to see whether it has previously been discussed. | ||||
|  | ||||
| If your change alters HTTPie’s behaviour or interface, it's a good idea to | ||||
| discuss it before you start working on it. | ||||
|   | ||||
							
								
								
									
										10
									
								
								README.rst
									
									
									
									
									
								
							
							
						
						
									
										10
									
								
								README.rst
									
									
									
									
									
								
							| @@ -36,7 +36,7 @@ You can select your corresponding HTTPie version as well as run examples directl | ||||
| browser using a `termible.io <https://termible.io?utm_source=httpie-readme>`_ embedded terminal. | ||||
|  | ||||
| If you are reading this on GitHub, then this text covers the current *development* version. | ||||
| You are invited to submit fixes and improvements to the the docs by editing | ||||
| You are invited to submit fixes and improvements to the docs by editing | ||||
| `README.rst <https://github.com/httpie/httpie/blob/master/README.rst>`_. | ||||
|  | ||||
|  | ||||
| @@ -159,7 +159,7 @@ Unstable version | ||||
| ---------------- | ||||
|  | ||||
| You can also install the latest unreleased development version directly from | ||||
| the ``master`` branch on GitHub.  It is a work-in-progress of a future stable | ||||
| the ``master`` branch on GitHub. It is a work-in-progress of a future stable | ||||
| release so the experience might be not as smooth. | ||||
|  | ||||
|  | ||||
| @@ -1319,7 +1319,7 @@ Viewing intermediary requests/responses | ||||
| --------------------------------------- | ||||
|  | ||||
| To see all the HTTP communication, i.e. the final request/response as | ||||
| well as any possible  intermediary requests/responses, use the ``--all`` | ||||
| well as any possible intermediary requests/responses, use the ``--all`` | ||||
| option. The intermediary HTTP communication include followed redirects | ||||
| (with ``--follow``), the first unauthorized request when HTTP digest | ||||
| authentication is used (``--auth=digest``), etc. | ||||
| @@ -1727,7 +1727,7 @@ headers and progress are still shown in the terminal: | ||||
|  | ||||
| .. code-block:: bash | ||||
|  | ||||
|     $ http -d https://github.com/httpie/httpie/archive/master.tar.gz |  tar zxf - | ||||
|     $ http -d https://github.com/httpie/httpie/archive/master.tar.gz | tar zxf - | ||||
|  | ||||
|  | ||||
|  | ||||
| @@ -2104,7 +2104,7 @@ Interface design | ||||
| ---------------- | ||||
|  | ||||
| The syntax of the command arguments closely corresponds to the actual HTTP | ||||
| requests sent over the wire. It has the advantage  that it’s easy to remember | ||||
| requests sent over the wire. It has the advantage that it’s easy to remember | ||||
| and read. It is often possible to translate an HTTP request to an HTTPie | ||||
| argument list just by inlining the request elements. For example, compare this | ||||
| HTTP request: | ||||
|   | ||||
| @@ -1,11 +1,8 @@ | ||||
| #!/usr/bin/env bash | ||||
|  | ||||
|  | ||||
| _http_complete() { | ||||
|     local cur_word=${COMP_WORDS[COMP_CWORD]} | ||||
|     local prev_word=${COMP_WORDS[COMP_CWORD - 1]} | ||||
|  | ||||
|     if [[ "$cur_word" == -*  ]]; then | ||||
|     if [[ "$cur_word" == -* ]]; then | ||||
|         _http_complete_options "$cur_word" | ||||
|     fi | ||||
| } | ||||
|   | ||||
		Reference in New Issue
	
	Block a user