Revisions to Editing a playlist configuration file

dropped a word that had a typo and wasn't necessary anyway

Source Link

edited Jan 8, 2016 at 11:26

Using sed to its fullest

sed is surprisingly powerful tool. For example:
```
  finddir=$(sed -n -E /"${sfile}_finddir"'/s/[^"]*\"([^"]*).*/\1/p' "${sdir}/config.cfg")
  [ -z ${finddir} ] && finddir=${d_finddir}
```
achieves the desired effect without any egrep.
- Requsted explanationExplanation: The last line ([ -z ]) tests whether finddir has zero length (meaning that sed didn't find the line in interest) and if so (&&) assigns it a default value.
Editing the config file

I am not sure I understand the decision to edit the config file via the script. It is much more natural (at least within the context provided) to edit it manually.

Using sed to its fullest

sed is surprisingly powerful tool. For example:
```
  finddir=$(sed -n -E /"${sfile}_finddir"'/s/[^"]*\"([^"]*).*/\1/p' "${sdir}/config.cfg")
  [ -z ${finddir} ] && finddir=${d_finddir}
```
achieves the desired effect without any egrep.
- Requsted explanation: The last line ([ -z ]) tests whether finddir has zero length (meaning that sed didn't find the line in interest) and if so (&&) assigns it a default value.
Editing the config file

I am not sure I understand the decision to edit the config file via the script. It is much more natural (at least within the context provided) to edit it manually.

Using sed to its fullest

sed is surprisingly powerful tool. For example:
```
  finddir=$(sed -n -E /"${sfile}_finddir"'/s/[^"]*\"([^"]*).*/\1/p' "${sdir}/config.cfg")
  [ -z ${finddir} ] && finddir=${d_finddir}
```
achieves the desired effect without any egrep.
- Explanation: The last line ([ -z ]) tests whether finddir has zero length (meaning that sed didn't find the line in interest) and if so (&&) assigns it a default value.
Editing the config file

I am not sure I understand the decision to edit the config file via the script. It is much more natural (at least within the context provided) to edit it manually.

added 197 characters in body

Source Link

edited Jan 4, 2016 at 21:37

Using sed to its fullest

sed is surprisingly powerful tool. For example:
```
  finddir=$(sed -n -E /"${sfile}_finddir"'/s/[^"]*\"([^"]*).*/\1/p' "${sdir}/config.cfg")
  [ -z ${finddir} ] && finddir=${d_finddir}
```
achieves the desired effect without any egrep.
- Requsted explanation: The last line ([ -z ]) tests whether finddir has zero length (meaning that sed didn't find the line in interest) and if so (&&) assigns it a default value.
Editing the config file

I am not sure I understand the decision to edit the config file via the script. It is much more natural (at least within the context provided) to edit it manually.

Using sed to its fullest

sed is surprisingly powerful tool. For example:

  finddir=$(sed -n -E /"${sfile}_finddir"'/s/[^"]*\"([^"]*).*/\1/p' "${sdir}/config.cfg")
  [ -z ${finddir} ] && finddir=${d_finddir}

achieves the desired effect without any egrep.

Editing the config file

I am not sure I understand the decision to edit the config file via the script. It is much more natural (at least within the context provided) to edit it manually.

Using sed to its fullest

sed is surprisingly powerful tool. For example:
```
  finddir=$(sed -n -E /"${sfile}_finddir"'/s/[^"]*\"([^"]*).*/\1/p' "${sdir}/config.cfg")
  [ -z ${finddir} ] && finddir=${d_finddir}
```
achieves the desired effect without any egrep.
- Requsted explanation: The last line ([ -z ]) tests whether finddir has zero length (meaning that sed didn't find the line in interest) and if so (&&) assigns it a default value.
Editing the config file

I am not sure I understand the decision to edit the config file via the script. It is much more natural (at least within the context provided) to edit it manually.

Source Link

answered Jan 4, 2016 at 20:23

Using sed to its fullest

sed is surprisingly powerful tool. For example:

  finddir=$(sed -n -E /"${sfile}_finddir"'/s/[^"]*\"([^"]*).*/\1/p' "${sdir}/config.cfg")
  [ -z ${finddir} ] && finddir=${d_finddir}

achieves the desired effect without any egrep.

Editing the config file

I am not sure I understand the decision to edit the config file via the script. It is much more natural (at least within the context provided) to edit it manually.

Return to Answer