From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Some questions about GPS Date: Mon, 23 Jul 2018 21:02:17 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <9f8bc09e-14a6-47a4-8083-caa1857ec6e9@googlegroups.com> NNTP-Posting-Host: IzvqdhUtDGKIMCldyDtZ+w.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 Content-Language: en-US X-Notice: Filtered by postfilter v. 0.8.3 Xref: reader02.eternal-september.org comp.lang.ada:53947 Date: 2018-07-23T21:02:17+02:00 List-Id: On 2018-07-23 20:26, Ian Douglas wrote: > Using GPS on Linux but some things driving me nuts, so need to determine if "that's the way it is" or is my configuration is flaky. > > 1. Line numbers: selected option for "all" but only first few are shown, then they stop. Some older versions had this bug, I remember. Reload the file/project and line numbers will reappear. > 2. When selecting text to copy/cut, it reverts to black on white when selected. I'm used to Kate where selected text gets a different background so you can clearly see what you've selected. Is this me or the way the editor works (and IMHO this is sub-optimal for usability). It can be changed in Edit->Preferences->Editor->Fonts & Colors. > 3. Am trying to read in a file, play with it, and write it out. So started with "Expanded with proper error handling and reporting it reads:" example (2nd one) on https://www.rosettacode.org/wiki/File_input/output#Line_by_line , but the compiler insists that the two "close input" statements are "unreachable code". The compiler is right. The loop is left only upon an exception, e.g. on the file end (End_Error) or on any other error. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de