General question: File not found

[Jan Erik Moström]

Hi,

I don't think this is a BBEdit problem, but using BBEdit was how I first discovered this. And it doesn't seem to happen with non-text files.

I have files in a folder hierarchy, when I double-click a file to open it I get this error message

> File not found (macOS error code: -43).

and

> File not found (macOS error code: -43).
>
> [CApplication.mm:5616]


First I thought it was a problem with Path Finder (which I normally use) but I get the same result when I try in Finder.

If I move the enclosing folder to the Desktop I get the same error, but if I move the file to the Desktop then I can open it. I tried open the file using TextEdit but it doesn't open the file (but I get no error message).

This doesn't happen all the time, sometimes it works. And everything seems just fine when using git, the files are checked in etc.

These are regular text files - markdown formatted with .md extension (I haven't seen this on any other files ... but I'm mostly using text files). My only guess here is that it

The files are all on the internal "disk", I'm using macOS 13.3.1 and Disk Utility says everything is OK.

However, I just discovered that there is one common thing for these files: they all have enclosing folders with the characters å, ä or ö in them, but this shouldn't be a problem should it? Or is it git that is doing something strange here?

I'm grateful for any advice.

= jem

[Bruce Van Allen]

I have the same experience. If I immediately repeat the “Open” command or double-click, the files open normally. Also doesn’t seem unique to BBEdit, and I still haven’t spotted a pattern, such as with the file hierarchy, behind the inconsistent behavior.

Pretty weird to see a file in the Finder, double-click it and have the OS say it can’t find the file.

— Bruce

_bruce__van_allen__santa_cruz_ca_

> --
> This is the BBEdit Talk public discussion group. If you have a feature request or need technical support, please email "sup...@barebones.com" rather than posting here. Follow @bbedit on Twitter: <https://twitter.com/bbedit>
> ---
> You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bbedit+un...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/bbedit/E1DD8C2D-129C-44DE-A5C4-9884720BABFD%40mostrom.pp.se.

[François Schiettecatte]

Not sure how relevant this is but I regularly lose access to my Documents folders, the Finder does not want to open it and I cannot access any files in it with any application, restarting the Finder is the only solution I have found that works.

Cheers

François

> To view this discussion on the web visit https://groups.google.com/d/msgid/bbedit/98B7A744-37C3-4FDF-88D6-CACE2A4EA453%40cruzio.com.

[iZann]

Ah, so glad to see this thread. Yes! This just recently started happening to me also. I do not think it has anything to do with BBEdit but probably has a lot to do with the Mac OS Finder. This has been happening to me now for less than a month — maybe a couple of weeks.

[Ron Catterall]

I've very recently seen the same when running in Terminal.

ls   -  listed the file OK

find  - couldn't see it

cat  - said file does not exis

logout/login  - all OK again

BBedit was NOT running, so this is not a BBedit problem.

To view this discussion on the web visit https://groups.google.com/d/msgid/bbedit/2c7b527a-64b9-474a-9423-adf591844ce4n%40googlegroups.com.

[Patrick Woolsey]

As a first step, please bring up BBEdit's Preferences window, select the Application pane and check to see whether sandbox access is allowed.

In case it is not, please grant access to BBEdit and then try performing your searches (etc.) again.


Regards,

Patrick Woolsey
==
Bare Bones Software, Inc. <https://www.barebones.com/>

> On May 06, 2023, at 05:16, Jan Erik Moström <li...@mostrom.pp.se> wrote:
>
> Hi,
>
> I don't think this is a BBEdit problem, but using BBEdit was how I first discovered this. And it doesn't seem to happen with non-text files.
>
> I have files in a folder hierarchy, when I double-click a file to open it I get this error message
>
>> File not found (macOS error code: -43).

> ... elided ... ]

[Patrick Woolsey]

PS: The below should correct any such errors you encounter when accessing files within BBEdit; it will not however cure the Finder or other apps.

Regards,

Patrick Woolsey
==
Bare Bones Software, Inc. <https://www.barebones.com/>

> --
> This is the BBEdit Talk public discussion group. If you have a feature request or need technical support, please email "sup...@barebones.com" rather than posting here. Follow @bbedit on Twitter: <https://twitter.com/bbedit>
> ---
> You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bbedit+un...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/bbedit/607D1705-F81A-48D4-8DD2-D2915D35E096%40barebones.com.

[Jan Erik Moström]

On 8 May 2023, at 15:19, Patrick Woolsey wrote:

> PS: The below should correct any such errors you encounter when accessing files within BBEdit; it will not however cure the Finder or other apps.

Too bad ... I kind of expected that BBEdit would fix all bugs everywhere 😜

Well, thanks to all who have answered, it feels better knowing that I'm not alone having this problem.

= jem