Solved Removal of '#' from sample code

[balanga]

Many posts provide examples of sample code for which I am very grateful, but one thing I often find myself doing is removing '#' from the start of the line when copying lines into some shell script.

How do others deal with removing this character?

Here is an example of what I mean:-

Chapter 5. The X Window System

This chapter describes how to install and configure the X Window System providing a graphical environment

docs.freebsd.org

Actually, I just noticed a number of these example have a small icon in the top right hand corner which copies the code to your clipboard.
Is this new as I never noticed it before.

 

[eternal_noob]

How do others deal with removing this character?

I open the editor and remove the characters in the lines. Very slowly and calmly, as a meditation exercise.

Of course, I could also use sed, but anyone can do that.

sed -i 's/^#//' filename

 

[SirDice]

but one thing I often find myself doing is removing '#' from the start of the line when copying lines into some shell script.

They are command prompts, the # indicates it's a root prompt. Like # pkg install drm-kmod

 

[Alain De Vos]

| grep -v ^\# | gawk 'NF'

 

[drhowarddrfine]

View: https://www.youtube.com/watch?v=3do07drusAs

 

[balanga]

They are command prompts, the # indicates it's a root prompt. Like # pkg install drm-kmod

Yes, I know they are prompts, but when you are copying and pasting them they are a pain.

I just noticed a little icon that copies the code to your clipboard. Is that a recent addition?

 

[SirDice]

Yes, I know they are prompts, but when you are copying and pasting them they are a pain.

You're supposed to copy/paste these to a prompt, the # of root's prompt kind of adds a layer of protection, as it's interpreted by the shell as a remark. It prevents accidentally copy/pasting something utterly destructive as root.

I just noticed a little icon that copies the code to your clipboard. Is that a recent addition?

Think it's always been there. But I don't read the handbook that often. It certainly was present on whole blocks of code/configuration files. Maybe they did add one for the single line command prompts too.

 

[MG]

It's backslash with me always. I mostly notice what happens. If things stop working suddenly, that's a typo in 1 of the last files.
You could use the locate-db to scan all files with shell code and check the first line,

 

[atax1a]

we don't copy it.

 

[cracauer@]

If you use Emacs you should check out the rectangular block cut'n'paste commands.

 

[atax1a]

multiple-cursors mode, too.