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!nntp-feed.chiark.greenend.org.uk!ewrotcd!newsfeed.xs3.de!io.xs3.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.109.57.87.72.mobile.3.dk!not-for-mail From: Jacob Sparre Andersen Newsgroups: comp.lang.ada Subject: Re: Some questions about GPS Date: Mon, 23 Jul 2018 21:01:31 +0200 Organization: JSA Research & Innovation Message-ID: <877elllqt0.fsf@adaheads.home> References: <9f8bc09e-14a6-47a4-8083-caa1857ec6e9@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: franka.jacob-sparre.dk; posting-host="109.57.87.72.mobile.3.dk:109.57.87.72"; logging-data="28704"; mail-complaints-to="news@jacob-sparre.dk" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) Cancel-Lock: sha1:sXuC4WN9EtPlKdAvcivTdCnLeJA= Xref: reader02.eternal-september.org comp.lang.ada:53946 Date: 2018-07-23T21:01:31+02:00 List-Id: Ian Douglas writes: > 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. Which version of GPS? The one currently packaged for Debian is indeed a bit flaky, while the one packaged with GNAT Community Edition, which you can download from AdaCore works quite well. > 1. Line numbers: selected option for "all" but only first few are > shown, then they stop. Wierd. > 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). I'm pretty sure that is a user setting (but I can't remember where/how you set it). > 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 two calls to "Close" just after "end loop" are indeed unreachable, and shouldn't be there. Greetings, Jacob -- "Very small. Go to sleep" -- monster (not drooling)