unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: arthur miller <arthur.miller@live.com>,
	Michael Heerdegen <michael_heerdegen@web.de>,
	help-gnu-emacs@gnu.org
Subject: RE: Jumping from one position to other position
Date: Sat, 5 Dec 2020 18:06:23 -0800 (PST)	[thread overview]
Message-ID: <334ec834-2f91-4eb8-b399-631dc745eb7e@default> (raw)
In-Reply-To: <AM0PR06MB6577EDBBA1AE97336CFC59BA96CF0@AM0PR06MB6577.eurprd06.prod.outlook.com>

To be clear, I don't expect anyone to recommend anything particular. Everything has advantages and disadvantages. And everyone has their use cases and preferences.

 

"FWIW" = "for what it's worth". It' similar to FYI. It has the connotation that it's really up to you (listener, not speaker) to judge how worthwhile you find the info to be.

 

.        https://dictionary.cambridge.org/us/dictionary/english/for-what-it-s-worth

.        https://www.merriam-webster.com/dictionary/for%20what%20it's%20worth

.        https://idioms.thefreedictionary.com/for+what+it%27s+worth

.        https://www.ahdictionary.com/word/search.html?q=for+what+it%27s+worth

 

(Oh, and FWIW ;-), https://en.wikipedia.org/wiki/For_What_It%27s_Worth.)

 

Drew, why am I not surprised Bookmark+ does that too? :-) 

 

I am sorry I didn't recommend your library, I had a feeling you will come in and point out Bookmark+ can do it better;  but I actually didn't know if it was applicable in this particular case.

 

By the way what FWIW stands for? For What I ...?


  reply	other threads:[~2020-12-06  2:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 18:23 Jumping from one position to other position Jean Louis
2020-12-05 22:11 ` Michael Heerdegen
2020-12-05 22:21   ` arthur miller
2020-12-05 22:54     ` Drew Adams
2020-12-06  0:55       ` arthur miller
2020-12-06  2:06         ` Drew Adams [this message]
2020-12-07  6:50     ` Jean Louis
2020-12-07 19:41       ` Arthur Miller
2020-12-07 20:26         ` Jean Louis
2020-12-05 23:38   ` Eric Abrahamsen
2020-12-06  0:12     ` Michael Heerdegen
2020-12-06  3:42       ` Eric Abrahamsen
2020-12-06 11:51         ` Stefan Möding
2020-12-06 18:15           ` Eric Abrahamsen
2020-12-06 23:07             ` Michael Heerdegen
2020-12-06 23:06         ` Michael Heerdegen
2020-12-06  5:41   ` Jean Louis
2020-12-06 23:11     ` Michael Heerdegen
2020-12-06  9:13   ` Marcin Borkowski
2020-12-06  2:12 ` Dmitry Gutov
     [not found] <<courier.000000005FCBD00B.00007ECE@static.rcdrun.com>
2020-12-05 21:29 ` Drew Adams
2020-12-06  5:24   ` Jean Louis
2020-12-06 23:25     ` Michael Heerdegen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=334ec834-2f91-4eb8-b399-631dc745eb7e@default \
    --to=drew.adams@oracle.com \
    --cc=arthur.miller@live.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).