Re: [anjuta-devel] Installed gtk+-3.2... Some problems

[John Coppens <john jcoppens com>]

On Thu, 10 Nov 2011 21:58:28 +0100
Sébastien Granjoux <seb sfo free fr> wrote:

> > That's representative to the state I'm in at the end of the semester...
> > Of course, that was 'Autotools' entries. When importing a project, I
> > get the options 'Directory', 'Makefile' and two 'Autotools'
>
> It could be because you have an old autotools plugin. You can delete 
> everything (at least all file with .plugin extension) in 
> /usr/local/lib/anjuta and reinstall anjuta.

Hi Sebastien,

I don't think so (Johannes suggested the same problem). I checked the
dates of all the plugins, and they correspond to the compilation
date/time. These are the autotools-related files left
in /usr/lib64/anjuta (anjuta was compiled with --prefix=/usr
--libdir=/usr/lib64):

anjuta-build-basic-autotools.plugin
libanjuta-build-basic-autotools.la  
libanjuta-build-basic-autotools.so

> > > > - More of nuisance - not really a bug: When deleting a file from
> > > > the disk while it's open in the editor. a dialog appears offering to
> > > > delete it (at least the button offers 'Delete').
> > > Could you file that as a bug please, doesn't harm much but should be fixed
>
> If I have understood correctly, I think it's the normal behavior. The 
> file is deleted on your disk so the data are only remaining in the 
> editor. The dialog appears to remind you this situation and the Delete 
> button will close the editor, discard the last remaining data.

I suggest that the button should have another caption - maybe 'Close
editor', or 'Close editor too' (or even 'Discard'). 'Delete' feels
contradictory to the message in the dialog that the file is already
deleted. I know it is just a semantic, but 'Delete' doesn't feel right.

John