Common Development Tasks

Adding a New Icon

1. Find the Unicode codepoint from the Nerd Fonts cheat sheet.
2. Add it to src/components/icons.rs:

   #![allow(unused)]
   fn main() {
   pub const MY_NEW_ICON: char = '\u{f0001}';
   }

3. Build — build.rs automatically subsets the font to include the new glyph.

Adding a New Config Option

1. Add the field to the relevant config struct in src/config.rs:

   #![allow(unused)]
   fn main() {
   #[derive(Deserialize, Clone, Debug)]
   #[serde(default)]
   pub struct MyModuleConfig {
       pub new_option: bool,  // Add this
   }
   }

2. Set a default value in the Default impl:

   #![allow(unused)]
   fn main() {
   impl Default for MyModuleConfig {
       fn default() -> Self {
           Self {
               new_option: false,
           }
       }
   }
   }

3. Use the option in your module.

4. If the option should be hot-reloadable, handle it in the module’s ConfigReloaded message.

Adding a D-Bus Integration

1. Create proxy definitions in a dbus.rs file:

   #![allow(unused)]
   fn main() {
   #[zbus::proxy(
       interface = "org.example.Service1",
       default_service = "org.example.Service",
   )]
   trait Service1 {
       #[zbus(property)]
       fn my_property(&self) -> zbus::Result<String>;
   }
   }

2. Implement the ReadOnlyService or Service trait.

3. Subscribe from a module. See Writing a New Service.

Working with the Theme

To add a new style or modify existing styles, edit src/theme.rs:

#![allow(unused)]
fn main() {
// Add a new button style method
pub fn my_button_style(&self) -> impl Fn(&Theme, Status) -> button::Style {
    let opacity = self.opacity;
    move |theme, status| {
        // Return button::Style based on status and theme
    }
}
}

Running Checks Before Committing

Always run the full check before pushing:

make check

This runs cargo fmt, cargo check, and cargo clippy -- -D warnings.

Debugging a Specific Module

To see debug output for a specific module:

# In config.toml
log_level = "warn,ashell::modules::my_module=debug"

Testing Config Hot-Reload

1. Start ashell: make start
2. Edit ~/.config/ashell/config.toml in another terminal
3. Save — changes should appear immediately
4. Check logs if changes don’t apply: tail -f /tmp/ashell/*.log