How to escape # character in #+begin_src bash block for html export?

How to escape # character in #+begin_src bash block for html export?

[Abigaile Johannesburg]

[-- Attachment #1: Type: text/plain, Size: 543 bytes --]

Dear community,

I have a minor question about how to escape '#' character in #+begin_src bash block. For example, when I export the source code block for bash, I can use

#+begin_src bash
$<some bash command for normal user>
#+end_src

But if I want to use # for indicating commands for root or privileged user, if I use 

#+begin_src bash
#<some bash command for root user>
#+end_src 

then the commands after '#' will be in italics, i.e., they are treated as comments in html export.

How do I solve this problem?

Thanks in advance. 

Abi

[-- Attachment #2: Type: text/html, Size: 785 bytes --]

Re: How to escape # character in #+begin_src bash block for html export?

[Michael Welle]

Hello,

Abigaile Johannesburg <abij@tuta.io> writes:

> Dear community,
>
> I have a minor question about how to escape '#' character in
> #+begin_src bash block. For example, when I export the source code
> block for bash, I can use
>
> #+begin_src bash
> $<some bash command for normal user>
> #+end_src
>
>
> But if I want to use # for indicating commands for root or privileged
> user, if I use
>
> #+begin_src bash
> #<some bash command for root user>
> #+end_src 
>
> then the commands after '#' will be in italics, i.e., they are treated
> as comments in html export.
>
> How do I solve this problem?
I'm not sure if I understand your problem correctly. # starts a comment
in shell, and $ denotes (among others maybe) a variable name. In that
sense 

#+begin_src bash
$ls
#+end_src

delivers the value of the variable ls. The semantic of $ is not to
execute the command ls as a non-root user. Same goes for #. If you want
to put your own semantics into $ and # it might be better to not use a
bash code block.

If you want to note that some commands in a script needs root privilege,
maybe something like this would do the trick:

#+begin_src bash
ls
su - -c 'fdisk /dev/rdsk/c0d1/p0'
emacs&
#+end_src

Regards
hmw

Re: How to escape # character in #+begin_src bash block for html export?

[Nick Dokos]

Michael Welle <mwe012008@gmx.net> writes:

> Hello,
>
> Abigaile Johannesburg <abij@tuta.io> writes:
>
>> Dear community,
>>
>> I have a minor question about how to escape '#' character in
>> #+begin_src bash block. For example, when I export the source code
>> block for bash, I can use
>>
>> #+begin_src bash
>> $<some bash command for normal user>
>> #+end_src
>>
>>
>> But if I want to use # for indicating commands for root or privileged
>> user, if I use
>>
>> #+begin_src bash
>> #<some bash command for root user>
>> #+end_src 
>>
>> then the commands after '#' will be in italics, i.e., they are treated
>> as comments in html export.
>>
>> How do I solve this problem?
> I'm not sure if I understand your problem correctly. # starts a comment
> in shell, and $ denotes (among others maybe) a variable name. In that
> sense 
>
> #+begin_src bash
> $ls
> #+end_src
>
>
> delivers the value of the variable ls. The semantic of $ is not to
> execute the command ls as a non-root user. Same goes for #. If you want
> to put your own semantics into $ and # it might be better to not use a
> bash code block.
>
> If you want to note that some commands in a script needs root privilege,
> maybe something like this would do the trick:
>
> #+begin_src bash
> ls
> su - -c 'fdisk /dev/rdsk/c0d1/p0'
> emacs&
> #+end_src
>
> Regards
> hmw
>
>

As Michael Welle points out

#+begin_src shell
# date
#+end_src

is a do-nothing source block since the command is commented out.

If you are trying to produce documentation and want to show commands
that the user should type then you probably need an example block:

#+begin_example 
# date
#+end_example

-- 
Nick

Re: How to escape # character in #+begin_src bash block for html export?

[Michael Welle]

Hello,

Nick Dokos <ndokos@gmail.com> writes:
[...]
> Michael Welle <mwe012008@gmx.net> writes:

> If you are trying to produce documentation and want to show commands
> that the user should type then you probably need an example block:
>
> #+begin_example 
> # date
> #+end_example
another idea: How about using shell code blocks for root commands as
well and attaching a CSS class to the block and colour the background?

Regards
hmw