So I use a "normal" floating environment (xfce, but could be another one), and I use Terminator in full screen enabled on a specific shortcut, so that I have tiled terminals.
2,087 karma · joined June 23, 2015
So I use a "normal" floating environment (xfce, but could be another one), and I use Terminator in full screen enabled on a specific shortcut, so that I have tiled terminals.
I would recommend:
- https://github.com/mozilla/gecko-dev/blob/af09c55c0e6253ba8f...
- https://github.com/mozilla/gecko-dev/blob/af09c55c0e6253ba8f...
> HeliBoard is a fork of OpenBoard, continuing the project from where it stopped.
I use [OpenBoard](https://f-droid.org/fr/packages/org.dslul.openboard.inputmet...), but there is no update since 2022 (it works well though).
You mean "disconnecting"? What was the error message in the console?
My provider is SFR (the only one giving access to optical fiber in the small village where I live).
EDIT: I'm talking about home internet. For mobile internet, I pay 19.99€/month for unlimited access (5G), but I haven't done a speedtest.
- https://github.com/libusb/libusb/issues/1468#issuecomment-19...
A canonical example could be about the "leap year" rules.
For context, the Earth makes a full rotation around the Sun in about 365.2425 days, so we use leap years to compensate:
- add 1 day every 4 years (365 + 1/4 = 365.25)
- but not every 100 years (365.25 - 1/100 = 365.24)
- but add a day anyway every 400 years (365.24 + 1/400 = 365.2425)
Suppose most people only know the first part (1 additional day every 4 years). If we ask "is 2000 a leap year?", they would answer "Of course, 2000 is a multiple of 4". And they would get the correct result.
Now, suppose someone started to study the "subject" (here, there is nothing to study, this is a trivial example for illustration), and is aware of the second rule (but not the third one). He would say "Ahah, no, 2000 is not a leap year, because it is a multiple of 100". But he would get the wrong answer.
My impression is that this kind of mistakes happens often while learning a subject: by studying, we encounter exceptions or surprising facts, that we may apply too broadly (to the point we make absurd claims, but that appear absurd for the wrong reasons).
Definitely not technical books.
I use it since I discovered it.
For example, this code (real world example from two days ago):
fn main() {
let value = None;
let _processed_value = match value {
Some(value) => Some(process(value)),
None => None,
};
}
fn process(_value: u32) {}
can be transformed into this equivalent form: fn main() {
let value = None;
let _processed_value = value.map(|value| process(value));
}
fn process(_value: u32) {}
But in async Rust, this code works: #[tokio::main]
async fn main() {
let value = None;
let _processed_value = match value {
Some(value) => Some(process(value).await),
None => None,
};
}
async fn process(_value: u32) {}
But this one does not work: #[tokio::main]
async fn main() {
let value = None;
let _processed_value = value.map(|value| process(value).await);
}
async fn process(_value: u32) {}
It fails with the following error: error[E0728]: `await` is only allowed inside `async` functions and blocks
--> src/main.rs:4:64
|
4 | let _processed_value = value.map(|value| process(value).await);
| ------- ^^^^^^ only allowed inside `async` functions and blocks
| |
| this is not `async`
This is basically what is described as the sandwich problem: https://blog.rust-lang.org/inside-rust/2022/07/27/keyword-ge...I have to admit that I often need to refactor parts of code while I'm writing Rust code due to such issues, so I understand the author's point of view.
> Can also plug in a keyboard and use that if you know the sequence.
For information, once the phone is unlocked and the authorization popup is open, the sequence to validate the authorization popup is Tab, Enter, Tab, Tab, Enter. The difficult part is to enable USB debugging to get the authorization popup without adb though.
Awesome, this feature was really missing.
> Votes must be received by 2022-10-01 23:59:59 UTC
(In fact, I just checked in Gnome, the menu does not expose microphone volume, it's only available from the settings window.)
> if nobody's looking, we are go
https://github.com/alcover/buffet/blob/dee3eb65f37ca07ea3d27...
And otherwise, when is it freed?
The refcount mechanism looks wrong to me: either the ownership of internal data is shared between instances (it seems it is not the case), either the owner is well defined and does not need a refcount.
It appears that the refcount is used to avoid freeing the owner data if Buffet views are still alive. But using the views after freeing the referenced data is incorrect usage anyway, so it looks like defensive programming, trading a use-after-free for a leak.