Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9016963
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 16, 20262026-06-16T04:08:29+00:00 2026-06-16T04:08:29+00:00

The Advanced Bash-Scripting Guide makes extensive use of multiline comments in examples, of the

  • 0

The Advanced Bash-Scripting Guide makes extensive use of multiline comments in examples, of the form:

echo ls -l | sh
#  Passes the output of "echo ls -l" to the shell,
#+ with the same result as a simple "ls -l".

(found in the explanation for the pipe | symbol). Other multiline comments look like this:

#!/bin/bash
# rpm-check.sh

#  Queries an rpm file for description, listing,
#+ and whether it can be installed.
#  Saves output to a file.
# 
#  This script illustrates using a code block.

(example 3.2 in the linked page).

What is the ratonale for the use of #+? Some multiline comments it seems to indicate that the comment continues on in the next line, but others it doesn’t.
Is there a ‘bash-scripting comment etiquette` that I should (attempt to) follow in my own scripts?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-16T04:08:30+00:00Added an answer on June 16, 2026 at 4:08 am

    It appears that the author of the Advanced Bash Scripting Guide uses that on lines which continue a sentence from the previous line.

    This is not a standard stylistic choice; this appears to be a stylistic quirk of the author of the Advanced Bash Scripting Guide.

    I will note that while there is some good technical information in the Advanced Bash Scripting Guide, the coding style is fairly non-standard. I wouldn’t use it as an example of what good Bash coding practices are. A somewhat better resource is the Bash FAQ.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

#!/bin/bash # This question is from advanced bash scripting guide section 5.1 echo var='(]\\{}\$\
TLDP's Advanced Bash Scripting Guide states that shell scripts shouldn't be used for situations
I have just printed and binded Advanced Bash Scripting guide . it had 800
I recently created a advanced form with elements that use jquery's $().hide & $().show
I use the following Bash Shell script to list the .txt files recursively under
I'm seeking suggestions for tools I can use on Windows to perform simple scripting
we are programming a bash like shell in C but we have problems with
Hey I want to create a bash-shell in wxPython, the only thing it should
really struggling with this one. I've recently setup a bash shell script to extract,
I'm trying to write my first semi advanced bash script that will take input

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.