* Remove the mutexes and have methods return the detected
  encoding.
* Try to handle the BOM safely...
* Clean up a bunch of code to make it more Zeddy

- Add a licence symlink to `encodings`

field of `Buffer`

- Implement `From` for `Encoding` and `Clone` for `EncodingOptions`

re-opened, while retaining the text.

- Fix an issue that prevented `InvalidBufferView` from being shown when
an incorrect encoding was chosen from the status bar.

- Centre the error message in `InvalidBufferView`.

`encodings`

- `EncodingWrapper` is replaced with `encodings::Encoding`

UI. The `encodings_ui` crate will only have UI related components in the
future.

choosing the correct encoding from `InvalidBufferView`

associated file was in a different encoding, rather than showing an
error.

bytes replaced with replacement characters

- Fix UTF-16 file handling

- Introduce a `ForceOpen` action to allow users to open files despite
encoding errors

- Add `force` and `detect_utf16` flags

- Update UI to provide "Accept the Risk and Open" button for invalid
encoding files

now open the file in the chosen encoding if it is valid or show the
invalid screen again if not.

(UTF-16 files aren't being handled correctly as of now)

- Remove the parameter from `BufferStore::open_buffer` as it is not
needed

- Pass encoding to `ProjectRegistry::open_path` and set the `encoding`
field in `Project`

encoding instead of replacing the invalid bytes with replacement
 characters

 - Add `encoding` field in `Workspace`

`InvalidBufferView`

one.

- Update the places where `File::load` is called

WARNING: The changes were committed with an error

changes to the file loading logic
- Add a module and an action in
`zed_actions` to open `EncodingSelector` from `InvalidBufferView`
- Add an `init` function in `encodings` crate to register the action handler

Clicking the second button in `InvalidBufferView` will cause the
`EncodingSelector` to be displayed. However, clicking on an encoding
currently does nothing.

- Simplify UTF-16 BOM detection

Co-authored-by: CrazyboyQCD

Release Notes:
- Add support for opening and saving files in different encodings and a setting to enable or disable the indicator

BOM is present

- Change `encoding` in `Buffer` to `Arc<Mutex<&\'static Encoding>>`

- Observe changes in the `encoding` field of `Buffer` and update the
status bar indicator

- Add UTF-16 LE and UTF-16 BE to encoding lists and mappings

- Implement encode/decode for UTF-16LE/BE in `EncodingWrapper`

- Remove unused serde deserialisation code and tests

- Remove unused dependencies

Co-authored-by: GitHub Copilot

- Add workspace-hack as a dependency

feat: Enable the user to choose whether or not the encoding indicator should be displayed by enabling or disabling `encoding_indicator` in `settings.json`

Modified `Buffer::reload` in `buffer.rs` to use this new function, allowing Zed
to open files with any encoding in UTF-8 mode. Files with characters that
are invalid in UTF-8 will have those bytes replaced with the � character.

Add comments and documentation.

feat: Add all supported encodings, and open the encoding selector when an action(save or reopen) is chosen.

This was inadvertently broken in v0.211.1-pre when we rewrote the
release build

Release Notes:

- N/A

Closes #41458 

Dynamically position mode selector tooltip to prevent clipping.

Position tooltip on the right when panel is docked left, otherwise on
the left. This ensures the tooltip remains visible regardless of panel
position.

**Note:** The tooltip currently vertically aligns with the bottom of the
menu rather than individual items. Would be great if it can be aligned
with the option it explains. But this doesn't seem trivial to me to
implement and not sure if it's important enough atm?

Before: 
<img width="431" height="248" alt="Screenshot 2025-10-30 at 22 21 09"
src="https://github.com/user-attachments/assets/073f5440-b1bf-420b-b12f-558928b627f1"
/>

After:
<img width="632" height="158" alt="Screenshot 2025-10-30 at 17 26 52"
src="https://github.com/user-attachments/assets/e999e390-bf23-435e-9df0-3126dbc14ecb"
/>
<img width="685" height="175" alt="Screenshot 2025-10-30 at 17 27 15"
src="https://github.com/user-attachments/assets/84efca94-7920-474b-bcf8-062c7b59a812"
/>


Release Notes:

- Improved the agent panel's mode selector by preventing it to go
off-screen in case the panel is docked to the left.

Currently, if a commit operation takes some time, there's no visual
feedback in the UI that anything's happening.

This PR changes the colour of the text on the button to the
`Color::Disabled` colour when a commit operation is pending.

Release Notes:

- Improved UI feedback when a commit is in progress

---------

Co-authored-by: Danilo Leal <daniloleal09@gmail.com>

Closes #38345, #34882, #33280

Debugpy has four distinct configuration scenarios, which are:
1. launch
2. attach with process id
3. attach with listen
4. attach with connect

Spawning Debugpy directly works with the first three scenarios but not
with "attach with connect". Which requires host/port arguments being
passed in both with an attach request and when starting up Debugpy. This
PR passes in the right arguments when spawning Debugpy in an attach with
connect scenario, thus fixing the bug.

The VsCode extension comment that explains this:
https://github.com/microsoft/vscode-python-debugger/blob/98f5b93ee4259f99b679d7c45163ba7babcbff6d/src/extension/debugger/adapter/factory.ts#L43-L51

Release Notes:

- debugger: Fix Python attach-based sessions not working with `connect`
or `port` arguments

Currently, this only applies to long-running individually selected
unstaged files in the git panel. Next up I would like to make this work
for `Stage All`/`Unstage All` however this will most likely require
pushing `PendingOperation` into `GitStore` (from the `GitPanel`).

Release Notes:

- N/A

We missed making extensions that provide agent servers fill the
`provides` field with `agent-servers`, and thus, filtering for this type
of extension in both the app and site wouldn't return anything.

Release Notes:

- N/A