Age | Commit message (Collapse) | Author |
|
Let's be reasonable and have a writable /etc by default.
|
|
|
|
Switch the comparisons from "other == *this" to "*this == other".
|
|
Named after the UIEvents specification that houses MouseEvent.
|
|
Some of these don't just use the REG bits of the mod/rm byte
as slashes, but also the R/M bits to have up to 9 different
instructions per opcode/slash combination (1 opcode requires
that MOD is != 11, the other 8 have MODE == 11).
This is done by making the slashes table two levels deep for
these cases.
Some of this is cosmetic (e.g "FST st0" has no effect already,
but its bit pattern gets disassembled as "FNOP"), but for
most uses it isn't.
FSTENV and FSTCW have an extraordinary 0x9b prefix. This is
not yet handled in this patch.
|
|
This reduces the size of the default build, while allowing people to
install as many ports as they want, without having to manually specify
disk size.
|
|
|
|
|
|
A serenity-style getpass that is thread-safe
|
|
|
|
This also makes String::split() give non-null strings when keep_empty is
true.
|
|
|
|
|
|
|
|
I was a bit confused by the fact that a method named `build_system_menu()`
first enumerates a directory. Moving the app/category discovery to a dedicated
function that returns the GUI-relevant information makes this process a bit
less surprising.
As an added bonus, `g_app_category_menus` was actually only a temporary mapping,
and didn't need to be global. In theory, SystemMenu should use a handful fewer
of bytes now.
|
|
|
|
It doesn't make sense for a top-level menu to have an icon, however
we do not have dedicated classes to distinguish these.
Furthermore, the only other place to store an icon is MenuItem.
Storing it there would be highly confusing, as MenuItem-with-Action
then would have two icons: one in Action and one in MenuItem.
And because we need to be able to replace the icon during realization,
this would need to write-through to Action somehow.
That's why I went with Menu, not MenuItem.
|
|
This factors out icon realization into its own function, making it possible to
use the same code with other classes that have icon() and set_icon() methods.
|
|
|
|
Inspector now opens ProcessChooser when no PID is supplied.
|
|
Moves ProcessChooser and RunningProcessesModel to LibGUI and
generalizes their construction for use by other apps. Updates
Profiler to reflect the change and use its new icons.
|
|
|
|
We were accidentally calling memset() on "addr" (the input char*), not
"dst_addr" (the target struct sockaddr_in), which was causing a simple
"nc localhost 8000" to crash.
Fixes #2908.
|
|
"0" was interpreted as a base-8 prefix, and the parse pointer was then
unconditionally advanced, causing us to consume zero characters.
This unbreaks the git port. :^)
(We should really have tests for LibC..)
|
|
This is enough to run /bin/ls :^)
|
|
Now that emulated processes have their real name (with a "(UE)" prefix)
we can actually let them know their name.
|
|
This being inline somehow broke the binutils autoconf scripts. It used
to work, so I suspect that some other change to LibC has caused those
autoconf scripts to go down a new path.
Regardless, this seems perfectly sensible.
|
|
This is very commonly used by terminal programs, and easy to support.
|
|
Just adding some basic folder/file icon makes a big difference here.
|
|
|
|
Makes `git status` less noisy for vim users.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I accidently wrote `Span<RemoveConst<T>>` when I meant
`Span<RemoveConst<T>::Type>`.
Changing that wouldn't be enough though, this constructor can only be
defined if T is not const, otherwise it would redefine the copy
constructor. This can be avoided by overloading the cast operator.
|
|
|
|
Use Core::guess_mime_type_based_on_filename() for this. It's obviously
not perfect, but it works better than just sending "text/html" for
everything no matter what. :^)
|
|
This could be useful in more places.
|
|
|
|
Use tables to align stuff instead of putting everything in a <pre>.
|
|
|
|
Note that these aren't full implementations of the bindings. This
mostly implements the low hanging fruit (namely, basic reflections)
There are some attributes that should be USVString instead of
DOMString. However, USVString is a slightly different definition
of DOMString, so it should suffice for now.
|