Jak używać znaczników Code?

Archiwalne, stare wpisy FAQ i HowTo Użytkowników
Awatar użytkownika
marcin1982
Moderator
Posty: 1703
Rejestracja: 05 maja 2011, 12:59
Lokalizacja: Zagłębie Dąbrowskie

Jak używać znaczników Code?

Post autor: marcin1982 » 10 grudnia 2014, 18:19

Zapewnie wielu z was czuje się poirytowanych faktem, że moderatorzy i administratorzy for wszelakich upominają i z uporem maniaka wymagają używania tzw. magicznych tagów Code.

Aby zobrazować zalety wynikające ze stosowania tych magicznych tagów posłużę się przykładem. Odpowiedzcie sobie na pytanie, który zapis jest dla was bardziej czytelny (przykładowy plik /etc/pacman.conf):

1. Tekst wstawiony na forum bez użycia jakiegokolwiek formatowania:

[marcin@archlinux ~]$ cat /etc/pacman.conf
#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
HoldPkg = pacman glibc
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta = 0.7
Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
# IgnorePkg = glib2

#NoUpgrade =
#NoExtract =

# Misc options
#UseSyslog
#Color
#TotalDownload
CheckSpace
#VerbosePkgLists

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
# SigLevel = Required DatabaseOptional
SigLevel = Never
# LocalFileSigLevel = Optional
# RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.

#
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

#[testing]
#Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

#[community-testing]
#Include = /etc/pacman.d/mirrorlist

[community]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

[archlinuxfr]
SigLevel = Never
Server = http://repo.archlinux.fr/x86_64

# =======================================================================#

# REPOZYTORIUM ŚRODOWISKA MATE
# [mate]
# SigLevel = Optional TrustAll
# Server = http://repo.mate-desktop.org/archlinux/$arch


# [core]
# Server = http://ftp.nluug.nl/pub/os/Linux/distr/ ... able/core/$arch

2. Tekst ujęty w tagi Code:

Kod: Zaznacz cały

[marcin@archlinux ~]$ cat /etc/pacman.conf
#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
HoldPkg     = pacman glibc
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta    = 0.7
Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg   =
#IgnoreGroup =
# IgnorePkg = glib2

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
#Color
#TotalDownload
CheckSpace
#VerbosePkgLists

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
# SigLevel = Required DatabaseOptional
SigLevel = Never
# LocalFileSigLevel = Optional
# RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

#[testing]
#Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

#[community-testing]
#Include = /etc/pacman.d/mirrorlist

[community]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

[archlinuxfr]
SigLevel = Never
Server = [URL]http://repo.archlinux.fr/x86_64[/URL]

# =======================================================================#

# REPOZYTORIUM ŚRODOWISKA MATE
# [mate]
# SigLevel = Optional TrustAll
# Server = http://repo.mate-desktop.org/archlinux/$arch


# [core]
# Server = http://ftp.nluug.nl/pub/os/Linux/distr/manjaro/unstable/core/$arch
Jak zatem tekst umieścić w tagach Code? Zajrzyjmy śmierci w oczy!

Sposób 1.

Podczas pisania postu wciskamy przycisk 'hash' # na pasku ikon okna edycji tekstu i pomiędzy znaczniki wklejamy tekst, który chcemy w nich umieścić.

Obrazek


Sposób 2.


Podczas pisania postu ręcznie wprowadzamy tagi Code - pokazują to obrazki poniżej:

Obrazek

Obrazek

W znacznikach "Code" należy ujmować ważne treści, a w szczególności wyniki poleceń z terminala, komendy polecane do wykonania innym użytkownikom, a także cytowane pliki / fragmenty plików konfiguracyjnych systemu.

Niechlujnie napisanym postem nikt się nawet nie zainteresuje, a wręcz powinien go zgłosić do moderacji.

ZAVRĚNO!

Zablokowany