Right now there's no way to set fixed colored cursor with escape sequence from inverted cursor, so it should be supported.

Hello there,
I just installed the latest version of broot 0.12.2 in iTerm Build 3.3.8 on a Mac OS Catalina 10.15.3.

It looks like a pretty amazing tool! Thanks for all the hard work*

One question, Alt+Enter is the default to bring the current windows into full size.
How can I change this? In the config file at /Users/USER/Library/Preferences/org.dystroy.broot/conf.toml, there is no Alt+

Description

Metadata changes do not raise the org.freedesktop.DBus.Properties.PropertiesChanged event

Compilation flags

• dbus_mpris
• dbus_keyring
• alsa_backend
• portaudi

Tokei counts blank lines inside comment blocks as blank lines. Wouldn't they be considered as comment lines?

For example:

/* Copyright (C) 2007-2008 Foo
   Copyright (C) 2008      Foo

   File: test.c
  
*/

Tokei output:

-------------------------------------------------------------------------------
 Language            Files        Lines         Code     Comment

We need a way to send system log streams for the kernel and all user-space components to external log collectors in real time.

For the EC2 AMI, we need to make it easy to stream logs to CloudWatch Logs.

Support for other log collectors can be added as well - it would be useful for interested users to indicate their preferences here and vote on them.

New debian-based distributions support the following:

deb [signed-by=6809F110790E0720856B562F744ACF4DF3319FFA] https://deriv.example.net/debian/ stable main

This is both, more secure, and allows to skip apt-key adv --recv-key (the latter also requires additional package on newer distros).

This is a bit more complex for UbuntuPPA though. Should we deprecate UbuntuPPA, or add microf

sudo-plugin, despite its generic name, currently only supports creating IO plugins, and not policy plugins. Would you consider policy plugins to be in-scope for the crate?

PS: Many thanks for releasing sudo-pair, and making sudo-plugin available as a reusable crate.

I just tried this out on Win7, with unexpected results:

Top is PowerShell, bottom is Cmder.

Not totally sure if it's the font, or wrong version of PowerShell.

Cargo.toml should probably have the licence in and inclusion in the root.

I think you want this in Cargo.toml:
license = "GPL-2.0-only"

Perhaps the AUTHORS file from busybox as well.

Great work!

The check() methods need a good review, to decide how they should actually be used and how errors should be handled at the high level.

Old bunch of the examples (removed at 7327b6d7097c5595d5121d48bd801bc016707e18) was not that good, as they were using internal APIs and worked with sub-crates directly, which led to confusion, since the intended way to work with heim is via facade crate.

Right now there is a bunch of new examples exist, but it would be nice to have more

in the code for getting windows exe path:
https://github.com/GuillaumeGomez/sysinfo/blob/master/src/windows/process.rs#L135-L153

MAX_PATH [...] is defined as 260 characters

The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters.

see here: https://docs.microsoft.com/en-us/windows/win32/fil

Seems that InnoSetup is included by default in AppVeyor to create the Windows installer. We should use it and automatically add it to our release. Some links:

• https://www.appveyor.com/docs/build-environment/
• http://help.appveyor.com/discussions/problems/4482-chocolatey-package-install-failure

Not really blaming this crate, but elaborating on pin numbering might be useful to the documentation reader.

I connected physical pin 24 on my Raspberry Pi 3, and now in hindsight, I think that pin really should be accessed via Pin 8, still not sure as SPI CS doesn't work as expected.

Output of gpio readall:

+-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-

@torch2424 ran into an issue with source being a relative path that started with ../.. and was outside the manifest directory. The error message they got was vague enough that there's no chance someone not familiar with the code would be able to spot the error.