Configuration de l’interpréteur de commandes : `.bashrc`, `.zshrc`, `.profile`

Ever wonder how your terminal knows your favorite shortcuts or custom look? It's thanks to shell configuration files!

These are special, hidden files in your home directory that tell your shell (like Bash or Zsh) how to behave and what to load every time you start a new session.

Configuring your shell is like setting up your perfect workspace. It allows you to:

• Automate tasks: Create shortcuts for long commands.
• Personalize appearance: Change your prompt to show useful info.
• Set up your environment: Define variables and paths for programs.

It makes your command line more efficient and enjoyable!

For Bash users, .bashrc is one of the most common config files. It runs every time you open a new interactive, non-login Bash shell (like opening a new terminal window).

It's the perfect place for:

• Defining aliases (command shortcuts).
• Creating shell functions.
• Customizing your shell prompt.

The .profile file is executed when you log in to your system. This often happens only once at the start of your session (e.g., after booting up and logging in, or connecting via SSH).

It's typically used for settings that should apply to *all* programs you run, not just your shell. Common uses include:

• Setting environment variables (like PATH).
• Defining system-wide configurations.

Understanding the difference is crucial:

• .bashrc: For interactive, non-login shells. Runs *every time* you open a new terminal. Best for shell-specific customizations (aliases, functions).
• .profile: For login shells. Runs *once* when you log in. Best for environment variables that affect all processes.

Often, .profile will source .bashrc for a consistent setup.

These files are plain text, so you can edit them with any text editor. A common choice in the terminal is nano.

To edit your Bash config, you'd type:

Remember to save your changes (Ctrl+O in nano) and exit (Ctrl+X).

After editing a config file, changes aren't active immediately. You need to tell your current shell to re-read the file.

This is done with the source command (or its shorthand, a single dot .):

Now, your shell will pick up the new settings without needing to open a new terminal window.

Aliases are short, custom commands that stand for longer ones. They're usually defined in .bashrc or .zshrc.

Example: To list all files including hidden ones, you might type ls -alF. An alias can shorten this:

After sourcing your config, you can just type ll!

For more complex tasks, shell functions are invaluable. They allow you to group multiple commands and use arguments.

Here's a simple function to create a directory and immediately change into it:

Add this to your .bashrc, source it, and then try mkcd mynewdir.

If you're a Zsh user, your primary configuration file is .zshrc. It serves a similar purpose to Bash's .bashrc.

Zsh is known for its powerful features and community frameworks like Oh My Zsh, which heavily relies on .zshrc for its plugins and themes.

You've learned about different shell configuration files and their purposes. Let's test your understanding!

Great job! You now understand how to configure your Linux shell.

• .bashrc/.zshrc: For interactive shell customizations (aliases, functions).
• .profile: For login-wide environment settings (like PATH).
• Use a text editor like nano to modify them.
• Apply changes with the source command.

Customizing your shell makes your terminal experience more powerful and personalized!