emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>,
	Org Mode <emacs-orgmode@gnu.org>
Subject: Re: function / way to get a global link to a file
Date: Fri, 13 Apr 2012 15:08:13 -0400	[thread overview]
Message-ID: <12966.1334344093@alphaville> (raw)
In-Reply-To: Message from Nick Dokos <nicholas.dokos@hp.com> of "Fri\, 13 Apr 2012 15\:04\:04 EDT." <12858.1334343844@alphaville>

Nick Dokos <nicholas.dokos@hp.com> wrote:

> Marcelo de Moraes Serpa <celoserpa@gmail.com> wrote:
> 
> > Hi list,
> > 
> > Within my personal productivity system that I've implemented using org, I used a main heading like this:
> > 
> > * tags :one:two:three:...
> > 
> > I use this in order to match a reference org file to other data that I have throughout my system, and it works great when I want to find all related information with a specific tag from the CLI by using ack or grep. This helps keeping things more organic, in the sense that I
> > don't have to think too much when capturing reference data (it can be a headline somewhere, or just a new org file in /refernece, important thing is that it has the proper semantics - i.e tags), but at the same time with enough structure to be useful. I could probably use
> > another notation, but that's the one I chose first, and all my reference files have it.
> > 
> > A problem I'm having however is that everytime I go to such org files and try to get a link to this file using C l, it creates a link to * tags. I then have to hit enter so that it brakes and creates a blank line in the top.
> > 
> > Is there  a way to always force copying a link *to the file*, instead of org trying to create a link to an item inside the file?
> > 
> 
> There is also a more permanent solution:

... that is, in addition to the C-u C-c l method that I sent to Marcelo without copying the list.
Apologies.

Nick

> 
> ,----
> | org-context-in-file-links is a variable defined in `org.el'.
> | Its value is t
> | 
> | Documentation:
> | Non-nil means file links from `org-store-link' contain context.
> | A search string will be added to the file name with :: as separator and
> | used to find the context when the link is activated by the command
> | `org-open-at-point'.  When this option is t, the entire active region
> | will be placed in the search string of the file link.  If set to a
> | positive integer, only the first n lines of context will be stored.
> | 
> | Using a prefix arg to the command C-c l (`org-store-link')
> | negates this setting for the duration of the command.
> | 
> | You can customize this variable.
> | 
> `----
> 

      reply	other threads:[~2012-04-13 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 18:44 function / way to get a global link to a file Marcelo de Moraes Serpa
2012-04-13 19:04 ` Nick Dokos
2012-04-13 19:08   ` Nick Dokos [this message]

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.orgmode.org/

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

  git send-email \
    --in-reply-to=12966.1334344093@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).